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

From Peter Eisentraut
Subject Re: "errno" not set in case of "libm" functions (HPUX)
Date
Msg-id 1306444402.27440.13.camel@vanquo.pezone.net
Whole thread Raw
In response to Re: "errno" not set in case of "libm" functions (HPUX)  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: "errno" not set in case of "libm" functions (HPUX)  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On tor, 2011-05-26 at 12:14 -0400, Tom Lane wrote:
> 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 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.

We could also do that globally, but that would probably be something for
the next release.




pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: inconvenient compression options in pg_basebackup
Next
From: "Kevin Grittner"
Date:
Subject: Re: [ADMIN] pg_class reltuples/relpages not updated by autovacuum/vacuum