Re: "errno" not set in case of "libm" functions (HPUX)
Peter Eisentraut <peter_e@gmx.net>
From: Peter Eisentraut <peter_e@gmx.net>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Ibrar Ahmed <ibrar.ahmad@gmail.com>, Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>, pgsql-hackers@postgresql.org
Date: 2011-05-26T21:13:22Z
Lists: 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.