Re: Strip -mmacosx-version-min options from plperl build
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Peter Eisentraut <peter.eisentraut@enterprisedb.com>
Cc: Andrew Dunstan <andrew@dunslane.net>,
pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2022-08-25T13:43:19Z
Lists: pgsql-hackers
Peter Eisentraut <peter.eisentraut@enterprisedb.com> writes: >>> In short: if the Cygwin Perl headers redefine PGDLLEXPORT (unlikely) >>> or somehow #define "__attribute__()" or "visibility()" into no-ops >>> (perhaps more likely) then we could explain this failure, and that >>> would also explain why it doesn't fail elsewhere. > This could be checked by running plperl.c through the preprocessor > (replace gcc -c plperl.c -o plperl.o by gcc -E plperl.c -o plperl.i) and > seeing what becomes of those symbols. Yeah, that was what I was going to suggest: grep the "-E" output for _PG_init and Pg_magic_func and confirm what their extern declarations look like. > If we want to get the buildfarm green again sooner, we could force a > --export-all-symbols directly. I'm not hugely upset as long as it's just the one machine failing. regards, tom lane
Commits
-
mingw: Define PGDLLEXPORT as __declspec (dllexport) as done for msvc
- 0e497eadb1f4 16.0 landed
-
Fix PL/Perl build on Cygwin
- 1c3aa54502dd 16.0 landed
-
Remove further unwanted linker flags from perl_embed_ldflags
- b4e936859dc4 16.0 landed