Re: Still a few flaws in configure's default CFLAGS selection - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Still a few flaws in configure's default CFLAGS selection
Date
Msg-id 12413.1066328307@sss.pgh.pa.us
Whole thread Raw
In response to Re: Still a few flaws in configure's default CFLAGS selection  (Bruce Momjian <pgman@candle.pha.pa.us>)
Responses Re: Still a few flaws in configure's default CFLAGS selection  (Bruce Momjian <pgman@candle.pha.pa.us>)
List pgsql-hackers
Bruce Momjian <pgman@candle.pha.pa.us> writes:
> The vote was whether -g should be used for a default compile.  Of course
> --enable-debug would continue using -g.  Maybe we kept --enable-debug
> for backward compatibility or to force -g if you modified CFLAGS?

I can't see why we would have kept --enable-debug if we intended to make
-g be default anyway.  Backwards compatibility is not an issue, because
configure simply ignores --enable switches it doesn't recognize (another
questionable autoconf design decision, but I digress).  And if you are
setting CFLAGS for yourself, you are surely capable of adding -g to it
if you want; why would you type seven times as much to accomplish the
same thing?
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: elog tab indentation
Next
From: Bruce Momjian
Date:
Subject: Re: Still a few flaws in configure's default CFLAGS selection