This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
Re: RFC --enable-debugging
- From: Brad Spencer <spencer at infointeractive dot com>
- To: Gabriel Dos Reis <gdr at integrable-solutions dot net>
- Cc: Phil Edwards <phil at jaj dot com>, Benjamin Kosnik <bkoz at redhat dot com>,libstdc++ at gcc dot gnu dot org
- Date: Wed, 6 Nov 2002 16:42:01 -0400
- Subject: Re: RFC --enable-debugging
- References: <u8hef89r7o.fsf@gromit.moeb> <20021029161117.A21995@disaster.jaj.com> <20021031174957.A15579@disaster.jaj.com> <20021031194119.548d7555.bkoz@redhat.com> <m365vgyb38.fsf@soliton.integrable-solutions.net> <20021031224637.A18172@disaster.jaj.com> <m3of98w1sg.fsf@soliton.integrable-solutions.net>
On Sat, Nov 02, 2002 at 02:15:27PM +0100, Gabriel Dos Reis wrote:
> Let me rephrase my question
>
> 1) Is there any automated way to have the compiler pick the debug
> library when a program is linked with -g?
As an everyday library user, I compile and link everything with -g
even when I build final release builds with full optimization so that
the debugging symbols are in the binary in the event of a crash. If
-g becomes overloaded to also mean "pick a non-optimized library
implementation", this could be a nasty surprise.
Perhaps I simply shouldn't be specifying -g on the _link_ line? I
prefer the explicit -L method. BTW, -g is currently not listed in the
gcc manual as an option that affects linking, AFAICT.
--
------------------------------------------------------------------
Brad Spencer - spencer@infointeractive.com - "It's quite nice..."
Systems Architect | InfoInterActive Corp. | A Canadian AOL Company