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 ...
I was trying to compile 8.2beta3 on openbsd, and ran into an interesting
issue. My account on the particular openbsd box has some restrictive
ulimit settings, so I don't have a lot of memory to work with. I was
getting an out of memory issue linking postgres, while I did not before.
I figured
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
