From: Andrew Haley <aph@redhat.com>
To: "Lalit Seth" <sethlalitwo@gmail.com>
Cc: gcc-help@gcc.gnu.org
Subject: Re: GCC COMPILE OPTIONS
Date: Fri, 10 Nov 2006 11:34:00 -0000 [thread overview]
Message-ID: <17748.25515.182669.450998@zebedee.pink> (raw)
In-Reply-To: <13d245450611100330s7ee0cda4q264c2fe687954185@mail.gmail.com>
Please don't top-post.
Lalit Seth writes:
> I have experienced that GCC fails to compile with gmake but gets
> successfully compiled when gmake bootstrap-lean is used. Why so.
Probably because your system compiler is broken.
> This was on HPUX 11.11 for version 3.3.2
>
> On 11/8/06, Tim Prince <timothyprince@sbcglobal.net> wrote:
> > Ian Lance Taylor wrote:
> > > "Lalit Seth" <sethlalitwo@gmail.com> writes:
> > >
> > >> I like to knw why we use "gmake bootstrap-lean" to compile GCC instead
> > >> of "gmake". How they are different and what behaviour changes are
> > >> there in 2 cases for GCC compiler.
> > >
> > > We have no idea why you do that.
> > >
> > > The difference is that during bootstrap-lean old stages are removed
> > > when they are no longer needed. That is, bootstrap-lean uses less
> > > disk space. There is no difference in the compiler.
> > >
> > I thought OP might be asking why it took so long for gcc build to
> > implement a default which should know when bootstrap is required. Only
> > the recent versions can build from scratch without explicit bootstrap
> > option.
> >
next prev parent reply other threads:[~2006-11-10 11:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-08 7:30 Lalit Seth
2006-11-08 15:54 ` Ian Lance Taylor
2006-11-08 17:32 ` Tim Prince
2006-11-10 11:30 ` Lalit Seth
2006-11-10 11:34 ` Andrew Haley [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-07-06 11:33 gcc compile options Peter Kurpis
2001-07-05 18:40 Peter Kurpis
2001-07-05 17:12 Carla Nunes
2001-07-05 18:15 ` Alexandre Oliva
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=17748.25515.182669.450998@zebedee.pink \
--to=aph@redhat.com \
--cc=gcc-help@gcc.gnu.org \
--cc=sethlalitwo@gmail.com \
/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).