This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Getting rid of -g
- To: Roman Lechtchinsky <rl at cs dot tu-berlin dot de>
- Subject: Re: Getting rid of -g
- From: Manfred Hollstein <manfred dot h at gmx dot net>
- Date: Wed, 12 Sep 2001 17:43:19 +0200
- CC: Franz Sirl <Franz dot Sirl-kernel at lauterbach dot com>, gcc at gcc dot gnu dot org, schwab at suse dot de
- References: <Pine.SOL.4.10.10109121625350.180-100000@sossusvlei>
- Reply-To: manfred dot h at gmx dot net
Roman Lechtchinsky wrote:
>
> On Wed, 12 Sep 2001, Manfred Hollstein wrote:
>
> > You should set stage1_cflags to -g0 in your case then.
>
> Unfortunately, Cray cc doesn't understand -g0. Besides, I'd rather avoid
> -g altogether (i.e. for libiberty etc. as well). Do I really have to do
> this individually for each package?
Put an override of STAGE1_CFLAGS into a host specific file in
config/<your-target-name>/x-<your-target-name> and then add the
name of this file to ${tmake_file} in gcc/config.gcc.
The only package which is compiled using plain cc is libiberty,
all other packages will be built using gcc, so there should be no
need to avoid using '-g' for those packages. Regarding libiberty,
you should create a similar config file in the libiberty/config
directory and put suitable code into libiberty/config.table.
But, I'd recommend to *not* ignore the value of ${CFLAGS} when
${CC} is set to something else than "cc".
>
> Bye
>
> Roman
HTH, cheers.
l8er
manfred