From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2012-04-07
Date: Sat, 14 Apr 2012 23:57:22 +0200 [thread overview]
Message-ID: <87y5pyase5.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <20120410085328.21507bc2@skate> (Thomas Petazzoni's message of "Tue, 10 Apr 2012 08:53:28 +0200")
>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:
Hi,
>> What toolchain is this? Gustavoz added uClibc patches for unshare
>> support, so if this is uClibc you'll need to rebuild the toolchain.
Thomas> Well, according to the defconfig, the toolchain is:
Thomas> BR2_TOOLCHAIN_CTNG=y
Thomas> BR2_TOOLCHAIN_CTNG_uClibc_LARGEFILE=y
Thomas> BR2_TOOLCHAIN_CTNG_uClibc_INET_IPV6=y
Thomas> BR2_TOOLCHAIN_CTNG_uClibc_INET_RPC=y
Thomas> BR2_TOOLCHAIN_CTNG_uClibc_LOCALE=y
Thomas> BR2_TOOLCHAIN_CTNG_CXX=y
Thomas> So it's a toolchain generated with our crosstool-NG backend, which
Thomas> apparently does not use the uClibc patches we have added for the
Thomas> internal backend.
No, it doesn't, and I seems nontrivial to me to make it do so as ctng
includes it's own patches which may conflict with "ours".
Doubling the safe/extra patches as patches-to-ctng (so
patches-to-patches) also isn't really nice.
Our ctng version is also still using 0.9.32.
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2012-04-14 21:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-08 6:30 [Buildroot] [autobuild.buildroot.net] Build results for 2012-04-07 Thomas Petazzoni
2012-04-08 7:10 ` Peter Korsgaard
2012-04-10 6:53 ` Thomas Petazzoni
2012-04-14 21:57 ` Peter Korsgaard [this message]
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=87y5pyase5.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.