From: Mark Fisher <fobs12@ymail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Status of external toolchain support
Date: Thu, 13 May 2010 12:29:21 +0000 (UTC) [thread overview]
Message-ID: <loom.20100513T141936-42@post.gmane.org> (raw)
In-Reply-To: 201005122347.39990.yann.morin.1998@anciens.enib.fr
Yann E. MORIN <yann.morin.1998@...> writes:
> > If you need to tell buildroot the type of threading used (linuxthread
> > old/new or nptl) then currently buildroot does not check that they match
> > up, as I have an nptl toolchain but am unable to select that in
> > buildroot so it is set to linuxthreads new, but I got no error.
>
> Oh, I see what you mean:
> - the prompt for the threading model is wrong when dealing with external
> toolchains: we only need to know if threads are supported or not
> - a check is missing to check coherency btw external toolchain threading
> capabilties, and buildroot configuration.
I think the problem is that the file toolchain\Config.in.2 is configured to
only allow BR2_THREADS_NATIVE (NPTL threading option) to be selected if uclibc
was set to the latest snapshot. This was a change made in February. It seems
like this selection should also be allowed if glibc is the C library.
>
> Regards,
> Yann E. MORIN.
>
Mark
next prev parent reply other threads:[~2010-05-13 12:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-12 17:15 [Buildroot] Status of external toolchain support Will Wagner
2010-05-12 21:19 ` Yann E. MORIN
2010-05-12 21:34 ` Grant Edwards
2010-05-12 21:53 ` Yann E. MORIN
2010-05-12 22:09 ` Grant Edwards
2010-05-12 21:36 ` Will Wagner
2010-05-12 21:47 ` Yann E. MORIN
2010-05-13 12:29 ` Mark Fisher [this message]
2010-05-13 15:22 ` Thomas Petazzoni
2010-05-13 17:21 ` Yann E. MORIN
2010-05-13 20:08 ` Thomas Petazzoni
2010-05-13 20:26 ` 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=loom.20100513T141936-42@post.gmane.org \
--to=fobs12@ymail.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