| From: | "F(dot) Laupretre" <flconseil(at)yahoo(dot)fr> |
|---|---|
| To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "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:15:52 |
| Message-ID: | ADECLLACEIPMLMCPIGGAEEAECCAA.flconseil@yahoo.fr |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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 optimization.
De : Tom Lane [mailto:tgl(at)sss(dot)pgh(dot)pa(dot)us]
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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | F. Laupretre | 2006-01-11 21:25:24 | Re: BUG #2162: Same as bug #1679 - finite() - unresolved symbol |
| Previous Message | Tom Lane | 2006-01-11 21:06:33 | Re: BUG #2162: Same as bug #1679 - finite() - unresolved symbol |