| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | Ibrar Ahmed <ibrar(dot)ahmad(at)gmail(dot)com>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: "errno" not set in case of "libm" functions (HPUX) |
| Date: | 2011-05-26 21:31:49 |
| Message-ID: | 8736.1306445509@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> On tor, 2011-05-26 at 12:14 -0400, Tom Lane wrote:
>> I tried this on my HP-UX 10.20 box, and it didn't work very nicely:
>> configure decided that the compiler accepted +Olibmerrno, so I got a
>> compile full of
>> cc: warning 450: Unrecognized option +Olibmerrno.
>> warnings. The reason is that PGAC_PROG_CC_CFLAGS_OPT does not pay any
>> attention to whether the proposed flag generates a warning. That seems
>> like a bug --- is there any situation where we'd want to accept a flag
>> that does generate a warning? I'm thinking that macro should set
>> ac_c_werror_flag=yes, the same way PGAC_C_INLINE does.
> I think so.
OK, committed with that addition.
> We could also do that globally, but that would probably be something for
> the next release.
Hmm. I'm a bit scared of how much might break. I don't think the
autoconf tests are generally designed to guarantee no warnings.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2011-05-26 21:50:00 | Re: [ADMIN] pg_class reltuples/relpages not updated by autovacuum/vacuum |
| Previous Message | Kevin Grittner | 2011-05-26 21:24:24 | Re: [ADMIN] pg_class reltuples/relpages not updated by autovacuum/vacuum |