Re: Exporting float_to_shortest_decimal_buf(n) with Postgres 17 on Windows
Andrew Kane <andrew@ankane.org>
From: Andrew Kane <andrew@ankane.org>
To: Nathan Bossart <nathandbossart@gmail.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, pgsql-hackers@postgresql.org
Date: 2024-09-13T22:26:42Z
Lists: pgsql-hackers
> Probably a Windows thing? Correct, it's only on Windows. > I do see a fair amount of special handling for f2s.c in the build files. I wonder if something got broken for Windows in the switch from the MSVC scripts to meson. This was my hunch as well since none of the source files changed. Also, neither function is present with `dumpbin /EXPORTS /SYMBOLS lib\postgres.lib`, which led me to believe it may need to be addressed upstream. - Andrew On Fri, Sep 13, 2024 at 2:41 PM Nathan Bossart <nathandbossart@gmail.com> wrote: > On Fri, Sep 13, 2024 at 04:58:20PM -0400, Tom Lane wrote: > > Andrew Kane <andrew@ankane.org> writes: > >> With Postgres 17 RC1 on Windows, `float_to_shortest_decimal_buf` and > >> `float_to_shortest_decimal_bufn` are not longer exported. This causes > >> `unresolved external symbol` linking errors for extensions that rely on > >> these functions (like pgvector). Can these functions be exported like > >> previous versions of Postgres? > > > > AFAICS it's in the exact same place it was in earlier versions. > > You might need to review your linking commands. > > I do see a fair amount of special handling for f2s.c in the build files. I > wonder if something got broken for Windows in the switch from the MSVC > scripts to meson. > > -- > nathan >
Commits
-
meson: Export all libcommon functions in Windows builds
- 643efb18bf80 16.7 landed
- d8b0c6411648 17.3 landed
- 07f902bd7607 18.0 landed
- 4e0d71ff2259 16.7 landed
- c80acbc6fae8 17.3 landed
- 2571c1d5cc5e 18.0 landed