| 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: | "Ed L(dot)" <pgsql(at)bluepolka(dot)net>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: 8.0.0beta2: gcc: unrecognized option `-pthreads' |
| Date: | 2004-09-11 02:12:53 |
| Message-ID: | 5157.1094868773@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> Tom Lane wrote:
>> Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
>>> No. The problem is that the test script just tries all options and if
>>> it doesn't error out, it uses it. Ideally we could test from configure
>>> and ingnore meaningless options but we don't know how yet.
>>
>> Drop any options that cause the compiler to write anything on stderr.
> OK, the configure test is:
BTW, I had some second thoughts about this later: if the compiler
generates warnings only for certain *combinations* of switches, it
seems likely that a simplistic test would get things wrong. Let's
try this patch, but be alert for possible problems.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2004-09-11 02:18:03 | Re: 8.0.0beta2: gcc: unrecognized option `-pthreads' |
| Previous Message | Bruno Wolff III | 2004-09-11 01:56:20 | Re: how to constrain a query to return 1 or 0 rows (or >1 or 0 rows) |