Re: Preventing abort() and exit() calls in libpq - Mailing list pgsql-hackers

From Jacob Champion
Subject Re: Preventing abort() and exit() calls in libpq
Date
Msg-id 67ddcb26f82acaffb26c59b7d8e4cd75399b2cd3.camel@vmware.com
Whole thread Raw
In response to Re: Preventing abort() and exit() calls in libpq  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Preventing abort() and exit() calls in libpq  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: Preventing abort() and exit() calls in libpq  (Peter Eisentraut <peter.eisentraut@enterprisedb.com>)
List pgsql-hackers
On Wed, 2021-06-30 at 18:29 -0400, Tom Lane wrote:
> I wrote:
> > Peter Eisentraut <peter.eisentraut@enterprisedb.com> writes:
> > > Could we set this rule up a little bit differently so that it is only 
> > > run when the library is built.
> > > Right now, make world on a built tree makes 17 calls to this "nm" line, 
> > > and make check-world calls it 81 times.  I think once would be enough. ;-)
> > Hmm, didn't realize that would happen.  Will see what can be done.
> 
> Looks like we'd have to make use of a dummy stamp-file, more or less
> as attached.  Any objections?

Spitballing -- if you don't like the stamp file, you could add the
check to the end of the $(shlib) rule, surrounded by an ifeq check.
Then .DELETE_ON_ERROR should take care of the rest, I think.

--Jacob

pgsql-hackers by date:

Previous
From: Jacob Champion
Date:
Subject: Re: [PATCH] Pull general SASL framework out of SCRAM
Next
From: Michael Paquier
Date:
Subject: Re: Dependency to logging in jsonapi.c