Re: FW: Building Postgres 17.0 with meson

On Thu, Nov 14, 2024 at 2:55 PM Mark Hill <Mark(dot)Hill(at)sas(dot)com> wrote:
> With openssl, zlib, and icu enabled in the setup, the ninja build fails trying to link src/backend/postgres.exe. There are 40 unresolved
> external symbol errors (see below.) I checked a few of the symbols and they appear in the Postgres source without the "_72" text on
> the end. Is it getting "72" from the version of icu4c I'm using, 72.1? Anyone know how to prevent these errors?

Yeah, I bet the library symbols are versioned. In general, I'd try to
figure out if you have more than one ICU install on the machine. Maybe
the versions are getting mixed somehow. More specifically, if this
were on Linux, I'd try to figure out which ICU library it's linking
against to get those symbols and run the appropriate tool on it to
list the symbols in that library. On Linux it would be nm. Then for
example where it's looking for u_strcpy_72 I would either find that
(a) the library contains u_strcpy rather than u_strcpy72, or (b) the
library contains u_strcpy_<some-other-number-here> rather than
u_strcpy_72, or (c) it doesn't contain any symbols even vaguely of
that sort.

--
Robert Haas
EDB: http://www.enterprisedb.com