From: Kai Ruottu <karuottu@mbnet.fi>
To: Andrew Bell <andrew.bell.ia@gmail.com>
Cc: gcc-help@gcc.gnu.org
Subject: Re: 4.2 build problem on redhat x86_64
Date: Fri, 30 Nov 2007 18:12:00 -0000 [thread overview]
Message-ID: <47503C7B.1030100@mbnet.fi> (raw)
In-Reply-To: <e80abd30711300733h7d9e3dd9m69a16be43522eda1@mail.gmail.com>
Andrew Bell wrote:
> I was trying to build gcc, but the process failed when trying to build
> the binutils that I linked in.
"Linked in"? Did you try to "combine" the binutils and GCC sources into
one "build tree" and then
configure and build them both at the same time?
The combining isn't that simple when binutils and GCC are separate
projects :( The same-name
subdirectories should be "in sync", suitable for both the binutils and
the GCC version. It would be
much better to configure and build these separately, one by one!
next prev parent reply other threads:[~2007-11-30 16:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-30 2:34 Andrew Bell
2007-11-30 3:27 ` Tim Prince
2007-11-30 15:33 ` Andrew Bell
2007-11-30 16:13 ` Andrew Bell
2007-11-30 18:12 ` Kai Ruottu [this message]
2007-11-30 23:20 ` Andrew Bell
2007-12-14 20:32 ` Michael Meissner
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=47503C7B.1030100@mbnet.fi \
--to=karuottu@mbnet.fi \
--cc=andrew.bell.ia@gmail.com \
--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).