Postgres Pro
Downloads
Home   >   mailing lists

Re: "errno" not set in case of "libm" functions (HPUX) - Mailing list pgsql-hackers

From Tom Lane
Subject Re: "errno" not set in case of "libm" functions (HPUX)
Date
Msg-id 24894.1306426478@sss.pgh.pa.us
Whole thread Raw
In response to Re: "errno" not set in case of "libm" functions (HPUX)  (Ibrar Ahmed <ibrar.ahmad@gmail.com>)
Responses Re: "errno" not set in case of "libm" functions (HPUX)  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-hackers
Tree view 
Ibrar Ahmed <ibrar.ahmad@gmail.com> writes:
> Please find the updated patch. I have added this "+Olibmerrno" compile flag
> check in configure/configure.in file.

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 ofcc: 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.
        regards, tom lane

pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: [ADMIN] pg_class reltuples/relpages not updated by autovacuum/vacuum
Next
From: Tom Lane
Date:
Subject: Re: [ADMIN] pg_class reltuples/relpages not updated by autovacuum/vacuum