From: Alexandre Oliva <aoliva@redhat.com>
To: Phil Edwards <pedwards@disaster.jaj.com>
Cc: gcc@gcc.gnu.org
Subject: Re: -B${prefix} during bootstrap
Date: Fri, 22 Sep 2000 11:59:00 -0000 [thread overview]
Message-ID: <or8zsktgms.fsf@guarana.lsd.ic.unicamp.br> (raw)
In-Reply-To: <20000921150050.A11167@disaster.jaj.com>
On Sep 21, 2000, Phil Edwards <pedwards@disaster.jaj.com> wrote:
> Why is -B$prefix passed to the stage1 compiler when building the stage2
> compiler? If $prefix isn't there yet (normal when bootstrapping, I would
> think), then what's the point?
The point is that sometimes it is there, and you actually need that to
get pre-installed headers. This is essential for a GCC+glibc
bootstrap.
> When bootstrapping with a previous gcc installed in the same $prefix, I
> once ended up with a permanently buggy toolchain.
This is no longer the case. The -B flags are now given in the right
order.
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicamp oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist *Please* write to mailing lists, not to me
next prev parent reply other threads:[~2000-09-22 11:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-09-21 11:56 Phil Edwards
2000-09-22 11:59 ` Alexandre Oliva [this message]
2000-09-22 12:27 ` Phil Edwards
2000-09-23 13:38 ` Jeffrey A Law
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=or8zsktgms.fsf@guarana.lsd.ic.unicamp.br \
--to=aoliva@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=pedwards@disaster.jaj.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).