public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Daniel.Egger@t-online.de (Daniel Egger)
To: Manfred Hollstein <manfred@s-direktnet.de>
Cc: egcs@cygnus.com
Subject: Re: Debugging flags
Date: Sun, 28 Jun 1998 12:37:00 -0000	[thread overview]
Message-ID: <98062813132301.00330@z2.n2480.f898.fidonet.org> (raw)
In-Reply-To: <13716.51728.315731.379406@saturn.hollstein.net>

On Sat, 27 Jun 1998, Manfred Hollstein wrote:

>each submake will
>use them, although\r their Makefile might contain different flags.

 That's the point. And I'm working to having the same flags in the whole
 process.... I just wonder why nobody had compiling problems due
 to this behaviour....

>Not, if you were working as suggested above.

 I think the ideal behaviour is the possibility to control everything by the
 configure script. Which isn't possbily right now. At the moment you
 have to export variables and hope that this will do the trick and no hardcoded
 flags are in your way. I still get those annoying -g's in bootstrapping process
 even if I set CFLAGS/CXXFLAGS accordingly. Not every user who's
 trying a official release of egcs knows how to override configure setting and
 won't know how to use a debugger either. So it's just rational to have
 a --disable-debug option to configure which will save lots of space and
 time without much fiddlings...

--

Servus,
       Daniel

      reply	other threads:[~1998-06-28 12:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-06-24 17:23 Daniel Egger
1998-06-25  9:19 ` Manfred Hollstein
1998-06-25 12:07   ` Joe Buck
1998-06-26 13:32   ` Daniel Egger
1998-06-26 22:48     ` Mumit Khan
1998-06-27  7:22     ` Manfred Hollstein
1998-06-28 12:37       ` Daniel Egger [this message]

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=98062813132301.00330@z2.n2480.f898.fidonet.org \
    --to=daniel.egger@t-online.de \
    --cc=egcs@cygnus.com \
    --cc=manfred@s-direktnet.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).