Re: sys_siglist[] is causing us trouble again
От | Tom Lane |
---|---|
Тема | Re: sys_siglist[] is causing us trouble again |
Дата | |
Msg-id | 3181175.1594856198@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: sys_siglist[] is causing us trouble again (Thomas Munro <thomas.munro@gmail.com>) |
Ответы |
Re: sys_siglist[] is causing us trouble again
|
Список | 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 по дате отправления: