| From: | Max Filippov <jcmvbkbc(at)gmail(dot)com> |
|---|---|
| To: | Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk> |
| Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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-03-20 10:57:44 |
| Message-ID: | CAMo8BfJmWC2eJSnA6gHXw4yT4LWGv+FpaHBiX=SZdJebXe-3Ew@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Mar 20, 2015 at 5:20 AM, Andrew Gierth
<andrew(at)tao11(dot)riddles(dot)org(dot)uk> wrote:
>>>>>> "Max" == Max Filippov <jcmvbkbc(at)gmail(dot)com> writes:
>
> Max> Sorry, I must be not clear enough: why checking compiler/linker
> Max> output instead of checking their exit code or presence of produced
> Max> object/ executable files?
>
> Going by the comment some lines above, my guess would be "because some
> compilers accept some option like -pthreads and issue a warning message
> saying that it is ignored, and pg wants to not treat such options as
> valid"
I've somehow missed that comment, thank you Andrew.
-- Max
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Max Filippov | 2015-03-20 11:01:56 | Re: configure can't detect proper pthread flags |
| Previous Message | Alvaro Herrera | 2015-03-20 10:55:02 | Re: btree_gin and ranges |