From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] Need some help with uClibc build
Date: Wed, 21 Jan 2009 07:24:40 +0100 [thread overview]
Message-ID: <87zlhltbvb.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <49768405.20909@hq.tensilica.com> (Maxim Grigoriev's message of "Tue\, 20 Jan 2009 18\:10\:13 -0800")
>>>>> "Maxim" == Maxim Grigoriev <maxim@tensilica.com> writes:
Maxim> Can somebody, please, help me.
Maxim> I seem to be missing something trivial like the fact that
Maxim> gcc-4.3.1+ would not work with uClibc-0.9.29, or something
Maxim> like this.
That could very well be - uClibc 0.9.29 is old, and gcc 4.3.x is
pretty new.
Maxim> I'm trying to build buildroot with
Maxim> binutils-2.19
Maxim> uClibc-0.9.29
Maxim> gcc-4.3.1
Why would you want to use those versions instead of the stable and
recommended ones? (uclibc 0.9.30, gcc 4.3.2)?
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2009-01-21 6:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-21 2:10 [Buildroot] Need some help with uClibc build Maxim Grigoriev
2009-01-21 6:24 ` Peter Korsgaard [this message]
2009-01-21 17:13 ` Maxim Grigoriev
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=87zlhltbvb.fsf@macbook.be.48ers.dk \
--to=jacmet@uclibc.org \
--cc=buildroot@busybox.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