From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] crosstool-ng and uClibc toolchain
Date: Fri, 2 Dec 2011 15:56:50 +0100 [thread overview]
Message-ID: <20111202155650.590ef8fd@skate> (raw)
In-Reply-To: <4ED8E43B.6020102@carallon.com>
Le Fri, 02 Dec 2011 14:44:11 +0000,
Will Wagner <will_wagner@carallon.com> a ?crit :
> In fact the uClibc config you are forced to use has lots of settings I
> would consider wrong.
>
> Am I correct thinking these things are broken or am I missing something?
I haven't fallen into these issues as I'm not using the ct-ng backend
a lot (I do use ct-ng outside of Buildroot in general).
> Am currently working on a patch that does the following:
> - Allow user to pick uClibc version when using ct-ng
> - Allow user to select nptl when using 0.9.32
> - Supply better default uClibc config files (Using same config files as
> for internal buildroot config)
> - Allow user to specify a custom uClibc config file
Those sounds like good ideas, especially the sharing the uClibc config
files between the internal build process and the ct-ng build process.
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2011-12-02 14:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-02 14:44 [Buildroot] crosstool-ng and uClibc toolchain Will Wagner
2011-12-02 14:56 ` Thomas Petazzoni [this message]
2011-12-02 21:25 ` Yann E. MORIN
2011-12-02 21:37 ` Michael S. Zick
2011-12-02 21:41 ` Yann E. MORIN
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=20111202155650.590ef8fd@skate \
--to=thomas.petazzoni@free-electrons.com \
--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