From: Roman Lechtchinsky <rl@cs.tu-berlin.de>
To: Manfred Hollstein <manfred.h@gmx.net>
Cc: Franz Sirl <Franz.Sirl-kernel@lauterbach.com>,
gcc@gcc.gnu.org, schwab@suse.de
Subject: Re: Getting rid of -g
Date: Thu, 13 Sep 2001 02:38:00 -0000 [thread overview]
Message-ID: <Pine.SOL.4.10.10109131130450.15733-100000@sossusvlei> (raw)
In-Reply-To: <3BA0799A.450BFA76@gmx.net>
On Thu, 13 Sep 2001, Manfred Hollstein wrote:
> Hmm... I'd suggest you add code to libiberty's aclocal.m4, which
> initializes a new autoconf variable ac_libiberty_debuginfo_cflags
> depending on whether the compiler is capable of generating proper
> code and debugging info or not; this doesn't necessarily mean that
> you have to actually compile code at configure time, but you can
> define its value based on some host specific libiberty/config/*
> file with a default of '-g' instead. This code should be added to the
> definition of the LIB_AC_PROG_CC function in a similar fashion as
> we are already doing for ac_libiberty_warn_cflags. libiberty's
> Makefile.in can then use this in the definition of COMPILE.c
Hmm, that will only work if libiberty's makefile doesn't use LIBCFLAGS
passed from the top level at all. I'm not sure if that's a good idea.
Maybe I should simply define a new variable, e.g. LIBIBERTYCFLAGS, in
libiberty's makefile, set it to LIBCFLAGS and use it in COMPILE.c instead
of LIBCFLAGS? This way, top-level LIBCFLAGS will still be used by default
but it will be possible to override it locally.
Bye
Roman
next prev parent reply other threads:[~2001-09-13 2:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-12 4:27 Roman Lechtchinsky
2001-09-12 4:50 ` Franz Sirl
2001-09-12 4:58 ` Roman Lechtchinsky
2001-09-12 5:41 ` Franz Sirl
2001-09-12 5:49 ` Roman Lechtchinsky
2001-09-12 6:09 ` Manfred Hollstein
2001-09-12 7:49 ` Roman Lechtchinsky
2001-09-12 8:44 ` Manfred Hollstein
2001-09-12 9:24 ` Roman Lechtchinsky
2001-09-12 10:06 ` Richard Henderson
2001-09-12 10:24 ` Roman Lechtchinsky
2001-09-12 10:49 ` Richard Henderson
2001-09-13 1:08 ` Roman Lechtchinsky
2001-09-13 2:25 ` Manfred Hollstein
2001-09-13 2:38 ` Roman Lechtchinsky [this message]
2001-09-12 6:48 ` Andreas Schwab
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.SOL.4.10.10109131130450.15733-100000@sossusvlei \
--to=rl@cs.tu-berlin.de \
--cc=Franz.Sirl-kernel@lauterbach.com \
--cc=gcc@gcc.gnu.org \
--cc=manfred.h@gmx.net \
--cc=schwab@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).