From: Dan Kegel <dank@kegel.com>
To: Beena <beena@gdatech.com>
Cc: Silverton Aron-C1710C <Aron.J.Silverton@motorola.com>,
"'Ashwin Bihari'" <raz0redge@hotmail.com>,
listmember@orkun.us, linuxppc-embedded@lists.linuxppc.org
Subject: Re: Cross-compile package combinations
Date: Thu, 11 Dec 2003 20:26:23 -0800 [thread overview]
Message-ID: <3FD9436F.2060206@kegel.com> (raw)
In-Reply-To: <FFELLIHDBBOAPGLCBDIPEEADCDAA.beena@gdatech.com>
Beena wrote:
> I have observed the same errors when trying to build the bootstrap gcc
> 3.2.3. I understand that
> this is because gcc 3.2.3 build (in case of powerpc) looks for some glibc
> files. So I first built gcc 2.95.3,
> then glibc 2.2.1 and then built bootstrap gcc 3.2.2(you could try with
> 3.2.3) and it compiled fine.
One of the reasons I did crosstool was to avoid that kind of
hackery. With crosstool, you don't need to build gcc 2.95.3
just to build gcc 3.2.3. Crosstool does clean builds from pristine,
minimally patched source.
- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-12-12 4:26 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-11 21:57 Cross-compile package combinations Silverton Aron-C1710C
2003-12-11 23:15 ` Beena
2003-12-12 4:26 ` Dan Kegel [this message]
2003-12-16 18:21 ` Beena
-- strict thread matches above, loose matches on Subject: below --
2003-12-16 19:34 Ashwin Bihari
2003-12-16 19:14 Silverton Aron-C1710C
2003-12-16 19:07 Ashwin Bihari
2003-12-16 18:53 Silverton Aron-C1710C
2003-12-16 20:14 ` Wolfgang Denk
2003-12-11 16:29 Ashwin Bihari
2003-12-11 14:29 Silverton Aron-C1710C
2003-12-11 0:28 Ashwin Bihari
2003-12-10 23:50 Silverton Aron-C1710C
2003-12-11 6:18 ` Dan Kegel
2003-12-11 16:06 ` listmember
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=3FD9436F.2060206@kegel.com \
--to=dank@kegel.com \
--cc=Aron.J.Silverton@motorola.com \
--cc=beena@gdatech.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=listmember@orkun.us \
--cc=raz0redge@hotmail.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 NNTP newsgroup(s).