Re: Strip -mmacosx-version-min options from plperl build

From: Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Strip -mmacosx-version-min options from plperl build
Date: 2022-08-25 13:01:14
Message-ID: c4afec71-ba16-c589-b094-66c2514afa4c@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 25.08.22 02:14, Andrew Dunstan wrote:
>> 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.
>>
>> I can't readily check this, since I have no idea exactly which version
>> of the Perl headers lorikeet uses.
>
> It's built against cygwin perl 5.32.
>
> I don't see anything like that in perl.h. It's certainly using
> __attribute__() a lot.

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.

If we want to get the buildfarm green again sooner, we could force a
--export-all-symbols directly.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2022-08-25 13:29:30 Re: [RFC] building postgres with meson - v11
Previous Message Michael Paquier 2022-08-25 12:21:47 Re: Avoid erroring out when unable to remove or parse logical rewrite files to save checkpoint work