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 01:08:00 -0000 [thread overview]
Message-ID: <Pine.SOL.4.10.10109130959001.15733-100000@sossusvlei> (raw)
In-Reply-To: <3B9F8297.90504901@gmx.net>
On Wed, 12 Sep 2001, Manfred Hollstein wrote:
> 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.
Nope, this doesn't work because both CFLAGS and LIBCFLAGS (it's the latter
which is actually used for compiling libiberty) are overridden by the
top-level makefile. I've added a Unicos-specific config file to the
top-level config directory and set host_makefile_frag in configure.in
appropriately. This seems to work but is this really the right way to do
it? Should I additionally do what you suggest to ensure that the correct
flags are passed if libiberty is built separately?
Bye
Roman
next prev parent reply other threads:[~2001-09-13 1:08 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 [this message]
2001-09-13 2:25 ` Manfred Hollstein
2001-09-13 2:38 ` Roman Lechtchinsky
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.10109130959001.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).