| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Mikael Sand <msand(at)seaber(dot)io> |
| Cc: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>, Aleksander Alekseev <aleksander(at)timescale(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Build issue with postgresql 17 undefined reference to `pg_encoding_to_char' and `pg_char_to_encoding' |
| Date: | 2024-10-10 19:07:48 |
| Message-ID: | 2665159.1728587268@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Mikael Sand <msand(at)seaber(dot)io> writes:
> Wonderful, the build works when using -lpgcommon_shlib -lpgport_shlib
> So this appears to imply that the output of `pkg-config -libs -static
> libpq`is incorrect?
>> /app # pkg-config -libs -static libpq
>> -L/usr/local/lib -lpq -L/usr/lib/llvm15/lib -L/usr/local/lib -lpgcommon
>> -lpgport -lgssapi_krb5 -lm -lldap -lssl -lcrypto -ldl -pthread
Hmm ... does seem that way. Peter apparently deliberately made it so
in 55392bc5b, but there's no real justification for removing _shlib
in the commit message. Peter?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mikael Sand | 2024-10-10 19:08:53 | Re: Build issue with postgresql 17 undefined reference to `pg_encoding_to_char' and `pg_char_to_encoding' |
| Previous Message | Mikael Sand | 2024-10-10 18:29:43 | Re: Build issue with postgresql 17 undefined reference to `pg_encoding_to_char' and `pg_char_to_encoding' |