From: "Frederick W. Wheeler" <wheeler@ipl.rpi.edu>
To: egcs@cygnus.com
Subject: Re: gas/gld installation during bootstrap -- how to unpack?
Date: Tue, 27 Oct 1998 18:13:00 -0000 [thread overview]
Message-ID: <199810272251.RAA00281@hpw1.cipr.rpi.edu> (raw)
EGCS list,
I think my last question was too brief. Here is a bit more
explanation of what I mean:
To have "make bootstrap" build and use gas and gld, should the
binutils-2.9.1 top-level source directory be in the egcs-1.1a
directory or should certain sub-directories and files from
binutils-2.9.1 be placed in egcs-1.1a?
Thanks again for your time,
Fred Wheeler
wheeler@ipl.rpi.edu
I wrote:
> EGCS list,
>
> I'd like to have "make bootstrap" build and use gas and gld, but I
> don't understand exactly what is meant by "if they have been properly
> unpacked into the egcs source tree" in the installation instructions I
> have quoted below.
>
> Thank you,
> Fred Wheeler
>
> From: http://egcs.cygnus.com/install/build.html
> > For a native build issue the command "make bootstrap". This will build
> > the entire egcs compiler system, which includes the following steps:
> >
> > Build host tools necessary to build the compiler such as texinfo,
> > bison, gperf.
> >
> > Build target tools for use by the compiler such as gas, gld, and
> > binutils if they have been properly unpacked into the egcs source
> > tree.
> >
> > Perform a 3-stage bootstrap of the compiler.
> >
> > Perform a comparison test of the stage2 and stage3 compilers.
> >
> > Build runtime libraries using the stage3 compiler from the
> > previous step.
next reply other threads:[~1998-10-27 18:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-10-27 18:13 Frederick W. Wheeler [this message]
1998-10-28 23:17 ` Alexandre Oliva
-- strict thread matches above, loose matches on Subject: below --
1998-10-27 16:33 Frederick W. Wheeler
1998-10-28 18:51 ` Joe Buck
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=199810272251.RAA00281@hpw1.cipr.rpi.edu \
--to=wheeler@ipl.rpi.edu \
--cc=egcs@cygnus.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).