From: Dominic Newton <dominic.newton@in-2-technology.co.uk>
To: buildroot@busybox.net
Subject: [Buildroot] Compiling problem with NPTL threads on x86
Date: Fri, 24 Jun 2011 18:46:20 +0100 [thread overview]
Message-ID: <4E04CD6C.3000200@in-2-technology.co.uk> (raw)
In-Reply-To: <4E037C99.2030308@in-2-technology.co.uk>
OK problem looks more or less solved.
NPTL threads are mainly supported by the latest uclibc release, but the
devil is in the detail. Some target architecture variants are not
supported. The buildroot menuconfig may show that NPTL threads are
available as an options, but when uclibc is configured the local logic
throws this out. A good check is to run uclibc-menuconfig and test out
the options on that.
So with this proviso I have compiled s basic system for a couple of
platforms with all thread variants and have tested each one - they work !
Dominic Newton
next prev parent reply other threads:[~2011-06-24 17:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-23 17:49 [Buildroot] Compiling problem with NPTL threads on x86 Dominic Newton
2011-06-24 17:46 ` Dominic Newton [this message]
2011-07-06 5:19 ` Peter Korsgaard
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=4E04CD6C.3000200@in-2-technology.co.uk \
--to=dominic.newton@in-2-technology.co.uk \
--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