From: White <white@from-b.org>
To: linuxppc-embedded@ozlabs.org
Subject: Re: buildroot uClibc busybox and associated tool versions
Date: Wed, 15 Mar 2006 17:58:08 +0100 [thread overview]
Message-ID: <20060315175808.2bd1ae70@White64> (raw)
In-Reply-To: <loom.20060314T023032-451@post.gmane.org>
Hi,
i'm using gcc 3.4.6
uclibc Release 0.9.28
busybox daily Snapshot.
With uclibc Snapshot i get an toolchain, but on the Target:
busybox init segfaults during init, at different points.
(but the snapshots uclibc build with gcc 4.1 and 4.2 :)
With gcc 4.x i get Compiler Errors, because of the weak aliases in
uclibc.
I test this last at 7.3
Would be nice to get Infos, which Combinations works...
Gcc 4.x would be nice to test.
Bye
next prev parent reply other threads:[~2006-03-15 16:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-14 1:48 buildroot uClibc busybox and associated tool versions Ben
2006-03-14 19:01 ` Peter Hanson
2006-03-15 16:58 ` White [this message]
-- 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=20060315175808.2bd1ae70@White64 \
--to=white@from-b.org \
--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).