Re: [HACKERS] configure can't detect proper pthread flags

2015-04-30 Thread Max Filippov
On Thu, Apr 30, 2015 at 3:51 PM, Robert Haas wrote: > On Wed, Apr 8, 2015 at 2:31 AM, Max Filippov wrote: >> On Sat, Mar 21, 2015 at 2:06 AM, Max Filippov wrote: >>> On Fri, Mar 20, 2015 at 3:43 PM, Max Filippov wrote: >>>> Ok, one more attempt: maybe instead of

Re: [HACKERS] configure can't detect proper pthread flags

2015-04-07 Thread Max Filippov
On Sat, Mar 21, 2015 at 2:06 AM, Max Filippov wrote: > On Fri, Mar 20, 2015 at 3:43 PM, Max Filippov wrote: >> Ok, one more attempt: maybe instead of checking that stderr is empty >> we could check that stderr has changed in the presence of the option >> that we test?

Re: [HACKERS] configure can't detect proper pthread flags

2015-03-20 Thread Max Filippov
On Fri, Mar 20, 2015 at 3:43 PM, Max Filippov wrote: > Ok, one more attempt: maybe instead of checking that stderr is empty > we could check that stderr has changed in the presence of the option > that we test? The patch: http://www.postgresql.org/message-id/1426860321-13586-1-git-s

[HACKERS] [PATCH] Compare linker/compiler output with their default output

2015-03-20 Thread Max Filippov
default. Signed-off-by: Max Filippov --- config/acx_pthread.m4 | 18 +- 1 file changed, 17 insertions(+), 1 deletion(-) diff --git a/config/acx_pthread.m4 b/config/acx_pthread.m4 index 581164b..028fdb1 100644 --- a/config/acx_pthread.m4 +++ b/config/acx_pthread.m4 @@ -79,6 +79,22

Re: [HACKERS] configure can't detect proper pthread flags

2015-03-20 Thread Max Filippov
On Fri, Mar 20, 2015 at 3:05 PM, Robert Haas wrote: > On Fri, Mar 20, 2015 at 7:01 AM, Max Filippov wrote: >> On Fri, Mar 20, 2015 at 6:08 AM, Tom Lane wrote: >>> We don't want every link step producing a useless warning. >>> Ideally, "make -s" would pr

Re: [HACKERS] configure can't detect proper pthread flags

2015-03-20 Thread Max Filippov
On Fri, Mar 20, 2015 at 6:08 AM, Tom Lane wrote: > We don't want every link step producing a useless warning. > Ideally, "make -s" would print nothing whatsoever; to the extent that > tools produce unsuppressable routine chatter, that's evil because it > makes it harder to notice actually-useful w

Re: [HACKERS] configure can't detect proper pthread flags

2015-03-20 Thread Max Filippov
On Fri, Mar 20, 2015 at 5:20 AM, Andrew Gierth wrote: >>>>>> "Max" == Max Filippov 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 > M

Re: [HACKERS] configure can't detect proper pthread flags

2015-03-19 Thread Max Filippov
On Fri, Mar 20, 2015 at 5:09 AM, Bruce Momjian wrote: > On Fri, Mar 20, 2015 at 04:51:55AM +0300, Max Filippov wrote: >> xtensa-linux-gcc -o conftest -Wall -Wmissing-prototypes >> -Wpointer-arith -Wdeclaration-after-statement -Wendif-labels >> -Wmissing-format-attribute -

Re: [HACKERS] configure can't detect proper pthread flags

2015-03-19 Thread Max Filippov
Hi Tom, On Fri, Mar 20, 2015 at 3:50 AM, Tom Lane wrote: > Max Filippov writes: >> when PostgreSQL is cross-compiled in the Buildroot with uClibc toolchain >> it may not correctly detect compiler/linker flags for threading. [1] >> The reason is that config/acx_pthread.m4:

[HACKERS] configure can't detect proper pthread flags

2015-03-19 Thread Max Filippov
Hi, when PostgreSQL is cross-compiled in the Buildroot with uClibc toolchain it may not correctly detect compiler/linker flags for threading. [1] The reason is that config/acx_pthread.m4:146 uses compiler and linker stdout and stderr to make decision if acx_pthread_ok should be yes or no: if te