From: steve@millersnet.net
To: gcc-help@gcc.gnu.org
Subject: Re: how to combine gcc and binutils source into one tree
Date: Mon, 30 Aug 2004 17:10:00 -0000 [thread overview]
Message-ID: <2087.192.168.0.4.1093884933.squirrel@nautilus.tsunami.us> (raw)
the linux kernel docs say use gcc 2.95.3 and the latest binutils. However
some packages like glibc won't build with 2.95.3 so you end up with 2
versions of gcc and 2 versions of binutils on the same system. While you
can manage this, should you get your wires crossed it could make for some
strange results. Perhaps I'm making the wrong approach, in the end I just
want two seperate toolchains. Since I will be putting both versions on
multiple machines I'm looking for a good way to package everything. I'll
post any success in doing this.
next reply other threads:[~2004-08-30 16:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-30 17:10 steve [this message]
2004-08-30 17:22 ` David Kramer
-- strict thread matches above, loose matches on Subject: below --
2004-08-30 17:42 steve
2004-08-30 18:28 ` David Kramer
2004-08-30 16:19 steve
2004-08-30 16:52 ` Eljay Love-Jensen
2004-08-30 17:04 ` David Kramer
2004-08-26 16:05 steve
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=2087.192.168.0.4.1093884933.squirrel@nautilus.tsunami.us \
--to=steve@millersnet.net \
--cc=gcc-help@gcc.gnu.org \
/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).