| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | hlinnaka(at)iki(dot)fi |
| Cc: | Max Filippov <jcmvbkbc(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk>, Bruce Momjian <bruce(at)momjian(dot)us>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, Peter Seiderer <ps(dot)report(at)gmx(dot)net> |
| Subject: | Re: configure can't detect proper pthread flags |
| Date: | 2015-07-08 17:50:22 |
| Message-ID: | 26630.1436377822@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Heikki Linnakangas <hlinnaka(at)iki(dot)fi> writes:
> The only scenario where you might now get warnings if we switch to
> upstream version, and didn't before, is if one of the flags makes
> pthreads to work, but also creates compiler warnings, while another flag
> later in the list would make it work without warnings. That's not
> totally inconceivable, but I doubt it happens. In any case, there's
> nothing PostgreSQL-specific about that, so if that happens, I'd like to
> find out so that we can complain to the upstream.
Actually, it looks like the modern version of ax_pthread.m4 adds -Werror
while testing, so that this should not be an issue anyway (at least on
compilers that accept -Werror).
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2015-07-08 19:27:33 | Re: Fillfactor for GIN indexes |
| Previous Message | Heikki Linnakangas | 2015-07-08 17:19:33 | Re: configure can't detect proper pthread flags |