Re: BUG #19095: Test if function exit() is used fail when linked static - Mailing list pgsql-bugs

From Nazir Bilal Yavuz
Subject Re: BUG #19095: Test if function exit() is used fail when linked static
Date
Msg-id CAN55FZ2Wqv+maXTfNO6+y=5400w7hCMo6RQhasqp=nrsODSBpg@mail.gmail.com
Whole thread Raw
In response to Re: BUG #19095: Test if function exit() is used fail when linked static  (Daniel Gustafsson <daniel@yesql.se>)
Responses Re: BUG #19095: Test if function exit() is used fail when linked static
List pgsql-bugs
Hi,

On Fri, 14 Nov 2025 at 15:11, Daniel Gustafsson <daniel@yesql.se> wrote:
>
> > On 12 Nov 2025, at 09:15, Michael Paquier <michael@paquier.xyz> wrote:
> >
> > On Wed, Nov 12, 2025 at 09:13:09AM +0100, Daniel Gustafsson wrote:
> >> On 12 Nov 2025, at 07:38, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> >>> Personally I'm okay with whitelisting pthread_exit() as
> >>> Torsten suggested.
> >>
> >> +1, we already have a few whitelisted entries and pthread_exit seems perfectly
> >> reasonable to add to that list.
> >
> > WFM.
>
> The attached trivial diff adds this to the whitelist clause in the Makefile.  I
> experimented with adding this to Meson, and while it's trivial enough to do the
> run_command with libpq_so.full_path, it's less clear to me exactly where in the
> build it should be added.  I've pinged my colleague Bilal who is much better at
> Meson than me to collaborate on that as a separate fix.

Sorry for the late reply. I replaced the Makefile portion with the
Perl script, so that it can be used for both meson and autoconf build
systems. The script takes two arguments

- input_file -> path of library file.
- stamp_file -> to create a stamp file for the meson build, so that
meson does not run while the library file is not changed. Autoconf
build does not use this option.

-- 
Regards,
Nazir Bilal Yavuz
Microsoft

Attachment

pgsql-bugs by date:

Previous
From: BharatDB
Date:
Subject: Re: BUG #19095: Test if function exit() is used fail when linked static
Next
From: Heikki Linnakangas
Date:
Subject: Re: pg_resetwal prints new OldestXID in wrong circumstances