Re: sys_siglist[] is causing us trouble again - Mailing list pgsql-hackers

From Tom Lane
Subject Re: sys_siglist[] is causing us trouble again
Date
Msg-id 3181175.1594856198@sss.pgh.pa.us
Whole thread Raw
In response to Re: sys_siglist[] is causing us trouble again  (Thomas Munro <thomas.munro@gmail.com>)
Responses Re: sys_siglist[] is causing us trouble again  (Andrew Dunstan <andrew.dunstan@2ndquadrant.com>)
List pgsql-hackers
Thomas Munro <thomas.munro@gmail.com> writes:
> On Thu, Jul 16, 2020 at 10:48 AM Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> Oddly, we'd not get to this code unless configure set
>> HAVE_DECL_SYS_SIGLIST, so it's defined *somewhere*.

> It looks like glibc very recently decided[1] to hide the declaration,
> but we're using a cached configure test result.

Ah, of course.  I was thinking that Peter had just changed configure
in the last day or so, but that did not affect the back branches.
So it's unsurprising for buildfarm animals to be using cached configure
results.

> I guess rawhide is the RH thing that tracks the bleeding edge?

Yup.  Possibly we should recommend that buildfarm owners running on
non-stable platforms disable autoconf result caching --- I believe
that's "use_accache => undef" in the configuration file.

Alternatively, maybe it'd be bright for the buildfarm script to
discard that cache after any failure (or at least configure or
build failures).

            regards, tom lane



pgsql-hackers by date:

Previous
From: Thomas Munro
Date:
Subject: Re: sys_siglist[] is causing us trouble again
Next
From: Dean Rasheed
Date:
Subject: Re: Infinities in type numeric