From: Paul Koning <pkoning@equallogic.com>
To: rene.rebe@gmx.net
Cc: drow@mvista.com, gcc@gcc.gnu.org
Subject: Re: building a gcc-3.3-prerelease cross-compiler
Date: Mon, 12 May 2003 16:59:00 -0000 [thread overview]
Message-ID: <16063.53985.772832.598267@pkoning.dev.equallogic.com> (raw)
In-Reply-To: <20030512.185423.115908471.rene.rebe@gmx.net>
>>>>> "Rene" == Rene Rebe <rene.rebe@gmx.net> writes:
Rene> Hi, On: Mon, 12 May 2003 10:22:38 -0400, Daniel Jacobowitz
Rene> <drow@mvista.com> wrote:
Rene> [ ... error log ... ]
>> > Any ideas?
>>
>> You can't build target libraries until after you've built glibc.
Rene> Well nice that the cross-build instructions change between
Rene> every major release (and sometimes between minors ...). What
Rene> are the current instructions?
Rene> (Is it intentional that the GCC install instructions point to
Rene> the rather old "Version: 1.01, Last Updated December 3, 1999"
Rene> CrossGCC/FAQ ? Maybe some more recent info should be included
Rene> in the install document ...)
Indeed. It would be even better if they actually worked. I have
never seen ones that work. The closest I have come is procedures that
result in a build process that aborts at some point, but gets far
enough to produce a compiler that appears to function.
paul
next prev parent reply other threads:[~2003-05-12 16:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-12 12:00 Rene Rebe
2003-05-12 14:22 ` Daniel Jacobowitz
2003-05-12 16:51 ` Rene Rebe
2003-05-12 16:59 ` Paul Koning [this message]
2003-05-12 19:24 ` Rene Rebe
2003-11-05 14:12 ` Rene Rebe
2003-05-13 15:46 ` Michael Eager
2003-05-13 16:07 ` Rene Rebe
2003-05-13 18:56 ` Michael Eager
2003-05-13 19:44 ` Rene Rebe
2003-05-13 20:34 ` Michael Eager
2003-05-13 22:14 ` Rene Rebe
2003-05-12 17:04 ` Joseph S. Myers
2003-05-12 17:13 ` Daniel Jacobowitz
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=16063.53985.772832.598267@pkoning.dev.equallogic.com \
--to=pkoning@equallogic.com \
--cc=drow@mvista.com \
--cc=gcc@gcc.gnu.org \
--cc=rene.rebe@gmx.net \
/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).