From: Ian Lance Taylor <ian@wasabisystems.com>
To: sashan <sashang@ihug.co.nz>
Cc: gcc@gcc.gnu.org
Subject: Re: [Newb] Building with debug info and no optimization
Date: Sat, 20 Mar 2004 04:29:00 -0000 [thread overview]
Message-ID: <m31xno2u9c.fsf@gossamer.airs.com> (raw)
In-Reply-To: <405B99BE.904@ihug.co.nz>
sashan <sashang@ihug.co.nz> writes:
> I'm trying to build gcc with debug info only so I do this at the
> command prompt
>
> export CFLAGS=-g
>
> I re-run configure to build the make file:
> gcc_current_build $ ../gcc_current/configure --program-suffix=-current
> gcc_current_build $ make
There is probably some way to make that approach work. However, the
easy way is to not set CFLAGS in the environment at all, and instead
do
make CFLAGS=-g
Ian
next prev parent reply other threads:[~2004-03-20 1:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-20 4:11 sashan
2004-03-20 4:29 ` Ian Lance Taylor [this message]
2004-03-30 1:16 ` Jim Wilson
2004-03-30 5:48 ` Mike Stump
2004-03-30 17:36 ` 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=m31xno2u9c.fsf@gossamer.airs.com \
--to=ian@wasabisystems.com \
--cc=gcc@gcc.gnu.org \
--cc=sashang@ihug.co.nz \
/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).