From: Michael S. Zick <minimod@morethan.org>
To: buildroot@busybox.net
Subject: [Buildroot] crosstool-ng and uClibc toolchain
Date: Fri, 2 Dec 2011 15:37:30 -0600 [thread overview]
Message-ID: <201112021537.33109.minimod@morethan.org> (raw)
In-Reply-To: <201112022225.07805.yann.morin.1998@anciens.enib.fr>
On Fri December 2 2011, Yann E. MORIN wrote:
> But I agree that the situation could be enhanced...
>
> > 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
> >
> > Assuming I can get it working I'll post it.
>
> Please, keep me in CC, so I do not miss the message...
>
In case you already missed it, five hours ago:
http://lists.busybox.net/pipermail/buildroot/2011-December/048033.html
Mike
next prev parent reply other threads:[~2011-12-02 21:37 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
2011-12-02 21:25 ` Yann E. MORIN
2011-12-02 21:37 ` Michael S. Zick [this message]
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=201112021537.33109.minimod@morethan.org \
--to=minimod@morethan.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