NetCube-Systems-Austria/kumquat-buildroot
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

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.

Browse Source
This commit is contained in:
"Steven J. Hill" 2007-04-28 17:10:31 +00:00
parent 4b2ebdb6d9
commit 4d4e1149eb
1 changed files with 25 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

27
toolchain/external-toolchain/Config.in
View File

@ -27,10 +27,10 @@ config BR2_TOOLCHAIN_EXTERNAL_STRIP
help
Strip shared libraries copied from the external toolchain.
source "toolchain/gdb/Config.in.2"
comment "Common Toolchain Options"
source "toolchain/gdb/Config.in.2"
config BR2_TOOLCHAIN_EXTERNAL_PATH
string "External toolchain path"
default ""
@ -44,6 +44,29 @@ config BR2_TOOLCHAIN_EXTERNAL_PREFIX
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