Re: BUG #2162: Same as bug #1679 - finite() - unresolved symbol - Mailing list pgsql-bugs

From F. Laupretre
Subject Re: BUG #2162: Same as bug #1679 - finite() - unresolved symbol
Date
Msg-id ADECLLACEIPMLMCPIGGAEEAECCAA.flconseil@yahoo.fr
Whole thread Raw
In response to Re: BUG #2162: Same as bug #1679 - finite() - unresolved symbol  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
I will also try these tests with '-O2' tomorrow (compile conftest and look =
if the symbol is still inside). I will even try more aggressive optimizatio=
n.

De : Tom Lane [mailto:tgl@sss.pgh.pa.us]

Bruce Momjian <pgman@candle.pha.pa.us> writes:
> Could any other configure tests fail in this way?

Good point.  The isinf() test probably has the same failure mode.

There is also the sigsetjmp() test, but since that has side-effects,
it doesn't seem very much at risk of being aggressively optimized.
I don't see any other cases where we're avoiding AC_CHECK_FUNC.

pgsql-bugs by date:

Previous
From: "F. Laupretre"
Date:
Subject: Re: BUG #2162: Same as bug #1679 - finite() - unresolved symbol
Next
From: Peter Eisentraut
Date:
Subject: Re: BUG #2162: Same as bug #1679 - finite() - unresolved symbol