From: Will Wagner <will_wagner@carallon.com>
To: buildroot@busybox.net
Subject: [Buildroot] crosstool-ng and uClibc toolchain
Date: Fri, 02 Dec 2011 14:44:11 +0000 [thread overview]
Message-ID: <4ED8E43B.6020102@carallon.com> (raw)
Hi,
I have been looking at building a toolchain using 2011.11 building it
with crosstools-ng and uClibc.
It currently seems a little bit broken/limited. I can supply a custom
ct-ng config, which specifies 0.9.32 but I am unable to select NPTL
threading or to specify a custom uClibc config file.
Also if I choose to use libthreads.new then the build fails as the
config file passed to build libc headers has no threading option
enabled. This problem is I think caused by the uClibc config file you
have to use. It contains LINUXTHREADS_OLD=y but there is not a not set
entry for LINUXTHREADS_NEW which means the sed command to set it can't work.
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?
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.
Thanks
Will
--
------------------------------------------------------------------------
Will Wagner will_wagner at carallon.com
Development Manager Office Tel: +44 (0)20 7371 2032
Carallon Ltd, Studio G20, Shepherds Building, Rockley Rd, London W14 0DA
------------------------------------------------------------------------
next reply other threads:[~2011-12-02 14:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-02 14:44 Will Wagner [this message]
2011-12-02 14:56 ` [Buildroot] crosstool-ng and uClibc toolchain Thomas Petazzoni
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=4ED8E43B.6020102@carallon.com \
--to=will_wagner@carallon.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 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.