From: sjhill at uclibc.org <sjhill@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot/toolchain/external-toolchain
Date: Sat, 28 Apr 2007 10:10:32 -0700 (PDT) [thread overview]
Message-ID: <20070428171032.29DB94808C@busybox.net> (raw)
Author: sjhill
Date: 2007-04-28 10:10:31 -0700 (Sat, 28 Apr 2007)
New Revision: 18529
Log:
When using an external toolchain, we still need to have the user select which thread model the toolchain was built with. This allows for proper building of LTP and possibly other packages.
Modified:
trunk/buildroot/toolchain/external-toolchain/Config.in
Changeset:
Modified: trunk/buildroot/toolchain/external-toolchain/Config.in
===================================================================
--- trunk/buildroot/toolchain/external-toolchain/Config.in 2007-04-28 17:09:44 UTC (rev 18528)
+++ trunk/buildroot/toolchain/external-toolchain/Config.in 2007-04-28 17:10:31 UTC (rev 18529)
@@ -27,10 +27,10 @@
help
Strip shared libraries copied from the external toolchain.
+comment "Common Toolchain Options"
+
source "toolchain/gdb/Config.in.2"
-comment "Common Toolchain Options"
-
config BR2_TOOLCHAIN_EXTERNAL_PATH
string "External toolchain path"
default ""
@@ -44,6 +44,29 @@
This the the external toolchain prefix. For example:
armeb-unknown-linux-gnu, mipsel-unknown-linux-gnu, etc.
+choice
+ prompt "Thread library implementation"
+ default BR2_EXT_PTHREADS_OLD
+ help
+ Select the version of libpthreads used in the external toolchain.
+
+ config BR2_EXT_PTHREADS_NONE
+ bool
+ prompt "none"
+
+ config BR2_EXT_PTHREADS
+ bool
+ prompt "linuxthreads"
+
+ config BR2_EXT_PTHREADS_OLD
+ bool
+ prompt "linuxthreads (stable/old)"
+
+ config BR2_EXT_PTHREADS_NATIVE
+ bool
+ prompt "Native POSIX Threading (NPTL)"
+endchoice
+
config BR2_LARGEFILE
bool "Enable large file (files > 2 GB) support?"
depends on !BR2_cris
next reply other threads:[~2007-04-28 17:10 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-28 17:10 sjhill at uclibc.org [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-01-12 12:54 [Buildroot] svn commit: trunk/buildroot/toolchain/external-toolchain laird at uclibc.org
2008-11-03 10:37 jacmet at uclibc.org
2008-11-03 10:32 jacmet at uclibc.org
2008-10-17 10:19 jacmet at uclibc.org
2008-06-16 12:22 jacmet at uclibc.org
2008-06-16 13:54 ` Bernhard Fischer
2008-06-16 14:07 ` Peter Korsgaard
2008-06-16 15:35 ` Bernhard Fischer
2008-06-17 4:23 ` Hamish Moffatt
2008-06-17 7:16 ` Peter Korsgaard
2008-06-17 10:47 ` Hamish Moffatt
2008-06-17 13:45 ` Peter Korsgaard
2008-06-17 14:29 ` Bernhard Fischer
2008-06-17 14:55 ` Peter Korsgaard
2008-06-17 15:45 ` Bernhard Fischer
2008-06-18 1:18 ` Hamish Moffatt
2008-06-18 7:36 ` Peter Korsgaard
2008-06-18 1:05 ` Hamish Moffatt
2007-07-17 0:18 sjhill at uclibc.org
2007-04-19 2:04 sjhill at uclibc.org
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=20070428171032.29DB94808C@busybox.net \
--to=sjhill@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox