Re: BUG #19095: Test if function exit() is used fail when linked static

VASUKI M <vasukim1992002@gmail.com>

From: VASUKI M <vasukim1992002@gmail.com>

To: Michael Paquier <michael@paquier.xyz>

Cc: Peter Eisentraut <peter@eisentraut.org>, Daniel Gustafsson <daniel@yesql.se>, Tom Lane <tgl@sss.pgh.pa.us>, BharatDB <bharatdbpg@gmail.com>, torsten.rupp@gmx.net, pgsql-bugs@lists.postgresql.org, byavuz81@gmail.com

Date: 2025-12-09T10:23:23Z

Lists: pgsql-bugs, pgsql-hackers

Thanks Michael and Peter for the detailed reviews and for taking the time
to refine and commit the updated version.

Thanks for pointing out that pgperltidy may behave differently across
environments.

On Tue, 9 Dec 2025 at 11:56, Michael Paquier <michael@paquier.xyz> wrote:

> The attached takes care of the issue here.  Adding that to pgxs_bins
> may look adapted at first glance, but I don't quite see the point in
> exposing this information to PGXS, so pgxs_empty is a better fit?
>
> Thanks for the clarification.Given that PGXS extensions don't appear to
require NM ,IMO adding it to pgxs_empty makes sense to me.It resolves the
Meson warning without exposing unnecessary variables to PGXS users.

Regards,
Vasuki M