From: "Ashwin Bihari" <raz0redge@hotmail.com>
To: Aron.J.Silverton@motorola.com, linuxppc-embedded@lists.linuxppc.org
Subject: RE: Cross-compile package combinations
Date: Wed, 10 Dec 2003 19:28:45 -0500 [thread overview]
Message-ID: <BAY9-F43XBirbThA9QR0004126e@hotmail.com> (raw)
Aron,
I've recently done just this, same host and target. I used GCC 3.2.3 with
GLIBC 2.3.2 w/ Linuxthreads and Binutils 2.14. This worked fine.
Check out a package called "crosstools". It's a nice tool that will tell you
about working combinations, actaully download these tarballs off the web,
find any applicable patches, apply them, configure the tools for your host
and target, build them and finally install it at your deisred location. All
this from running a single SHELL file. This is what I did and it worked like
a charm.
I've currently used this toolchain to compile 2.4.x kernels, haven't tried
2.6.x.
Contact me if you want any more details.
~Ashwin
_________________________________________________________________
Winterize your home with tips from MSN House & Home.
http://special.msn.com/home/warmhome.armx
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next reply other threads:[~2003-12-11 0:28 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-11 0:28 Ashwin Bihari [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-12-16 19:34 Cross-compile package combinations 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 21:57 Silverton Aron-C1710C
2003-12-11 23:15 ` Beena
2003-12-12 4:26 ` Dan Kegel
2003-12-16 18:21 ` Beena
2003-12-11 16:29 Ashwin Bihari
2003-12-11 14:29 Silverton Aron-C1710C
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=BAY9-F43XBirbThA9QR0004126e@hotmail.com \
--to=raz0redge@hotmail.com \
--cc=Aron.J.Silverton@motorola.com \
--cc=linuxppc-embedded@lists.linuxppc.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 NNTP newsgroup(s).