From: Ben <Ben@haliplex.com>
To: linuxppc-embedded@ozlabs.org
Subject: buildroot uClibc busybox and associated tool versions
Date: Tue, 14 Mar 2006 01:48:22 +0000 (UTC) [thread overview]
Message-ID: <loom.20060314T023032-451@post.gmane.org> (raw)
Hi all
Im looking for some info on what versions of uClibc , busybox , gcc , binutils
and kernel headers are best to use to build up a toolchain and rootfs for a 82xx
PPC.
I am using buildroot http://buildroot.uClibc.org to generate the toolchain
associated tools and rootfs but so far have not had much luck.
The host machine i am compiling on is a dell poweredge 650 xeon server running
Fedora Core 3, it has gcc 3.4.2-6 binutils-2.15.92.0.2 glibc-2.3.3 and
linux version 2.6.9-1.667.
Im trying to compile up a rootfs for 82xx PPC with the following
gcc 4.0.2
binutils 2.16.1
Kernel headers 2.16.12
uClibc - whatever version works best, right now i have daily snapshot 20060113
busybox - whatever version works best, right now i have snapshot from 9th march
and am applying patches released from 9th march - 13th march.
Personally i think the choices of gcc , binutils and Kernel headers are fine, i
seem to be having more trouble with the uClibc ver and busybox ver.
Last Friday 10th march selecting the daily snapshot of uClibc caused the
compilation to not get past the point of generating gcc and bin utils. Using the
daily snapshot version of busybox also caused compilation to fail with it
reporting lots of .os and .osm files missing in the libbb dir until i applied
todays patches.
Ive also tried building with use daily snapshot unchecked for busybox and uClibc
but compilation fails.
Surely someone out there must know what versions of everything are the best to
use to generate a toolchain and rootfs for PPC.
Any help anyone could give would be greatly appreciated
next reply other threads:[~2006-03-14 3:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-14 1:48 Ben [this message]
2006-03-14 19:01 ` buildroot uClibc busybox and associated tool versions Peter Hanson
2006-03-15 16:58 ` White
-- strict thread matches above, loose matches on Subject: below --
2006-03-14 7:54 IGOR LURI
2006-03-15 21:36 Harald Küthe
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=loom.20060314T023032-451@post.gmane.org \
--to=ben@haliplex.com \
--cc=linuxppc-embedded@ozlabs.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).