From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] Compiling problem with NPTL threads on x86
Date: Wed, 06 Jul 2011 07:19:07 +0200 [thread overview]
Message-ID: <87box8ugtw.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <4E04CD6C.3000200@in-2-technology.co.uk> (Dominic Newton's message of "Fri, 24 Jun 2011 18:46:20 +0100")
>>>>> "Dominic" == Dominic Newton <dominic.newton@in-2-technology.co.uk> writes:
Dominic> OK problem looks more or less solved.
Dominic> NPTL threads are mainly supported by the latest uclibc release, but
Dominic> the devil is in the detail. Some target architecture variants are not
Dominic> supported. The buildroot menuconfig may show that NPTL threads are
Dominic> available as an options, but when uclibc is configured the local logic
Dominic> throws this out. A good check is to run uclibc-menuconfig and test out
Dominic> the options on that.
What configurations are those? Perhaps we can improve the menuconfig
logic in buildroot.
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2011-07-06 5:19 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
2011-07-06 5:19 ` 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=87box8ugtw.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.