Re: BUG #2162: Same as bug #1679 - finite() - unresolved symbol

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: flconseil(at)yahoo(dot)fr, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #2162: Same as bug #1679 - finite() - unresolved symbol
Date: 2006-01-11 21:06:33
Message-ID: 28138.1137013593@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)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.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message F. Laupretre 2006-01-11 21:15:52 Re: BUG #2162: Same as bug #1679 - finite() - unresolved symbol
Previous Message Bruce Momjian 2006-01-11 21:03:04 Re: BUG #2162: Same as bug #1679 - finite() - unresolved symbol