| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Ibrar Ahmed <ibrar(dot)ahmad(at)gmail(dot)com> |
| Cc: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, pgsql-hackers(at)postgresql(dot)org, Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Subject: | Re: "errno" not set in case of "libm" functions (HPUX) |
| Date: | 2011-05-26 16:14:38 |
| Message-ID: | 24894.1306426478@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2011-05-26 16:23:02 | Re: [ADMIN] pg_class reltuples/relpages not updated by autovacuum/vacuum |
| Previous Message | panam | 2011-05-26 16:08:07 | Re: Hash Anti Join performance degradation |