Re: "errno" not set in case of "libm" functions (HPUX)

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
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:13:22
Message-ID: 1306444402.27440.13.camel@vanquo.pezone.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On tor, 2011-05-26 at 12:14 -0400, Tom Lane wrote:
> Ibrar Ahmed <ibrar(dot)ahmad(at)gmail(dot)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.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Kevin Grittner 2011-05-26 21:24:24 Re: [ADMIN] pg_class reltuples/relpages not updated by autovacuum/vacuum
Previous Message Tom Lane 2011-05-26 21:11:12 Re: inconvenient compression options in pg_basebackup