From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> |
Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Strip -mmacosx-version-min options from plperl build |
Date: | 2022-08-25 13:43:19 |
Message-ID: | 1465158.1661434999@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2022-08-25 13:50:18 | Re: pg_regress: lookup shellprog in $PATH |
Previous Message | Peter Eisentraut | 2022-08-25 13:42:40 | postgres_fdw hint messages |