Re: [HACKERS] beta3 CFLAGS issue on openbsd

2006-11-10 Thread Peter Eisentraut
Am Freitag, 10. November 2006 08:29 schrieb Jeremy Drake:
 I figured out that the -g flag was being surreptitiously added to my
 CFLAGS.  It was like pulling teeth trying to get the -g flag out.  I tried
 --disable-debug to configure, which did not work.  I had to do
 CFLAGS=-O2 ./configure ...

Apparently you have some CFLAGS setting in your environment.

-- 
Peter Eisentraut
http://developer.postgresql.org/~petere/

---(end of broadcast)---
TIP 7: You can help support the PostgreSQL project by donating at

http://www.postgresql.org/about/donate


Re: [HACKERS] beta3 CFLAGS issue on openbsd

2006-11-09 Thread Tom Lane
Jeremy Drake [EMAIL PROTECTED] writes:
 I figured out that the -g flag was being surreptitiously added to my
 CFLAGS.  It was like pulling teeth trying to get the -g flag out.

I believe that this is a default behavior of autoconf scripts.
I remember having done some ugly hacks years ago to prevent an autoconf
configure script from adding -g by default to libjpeg builds... and
the argument for not having -g has gotten ever weaker since then,
so I really doubt you'll get far complaining to the autoconf maintainers
about it.

regards, tom lane

---(end of broadcast)---
TIP 1: if posting/reading through Usenet, please send an appropriate
   subscribe-nomail command to [EMAIL PROTECTED] so that your
   message can get through to the mailing list cleanly