Move config files around, and clean up the mess in the config/ directory.
config/kernel/kernel_linux.in | 12 6 6 0 +-
config/paths.in | 89 0 89 0 ----------------
config/kernel_linux_headers_install.in | 168 0 168 0 ------------------------------
config/kernel.in | 2 1 1 0
config/kernel_linux_headers_copy.in | 42 0 42 0 --------
config/cc.in | 2 1 1 0
config/logging.in | 110 0 110 0 --------------------
config/build-behave.in | 45 0 45 0 --------
config/libc_uClibc.in | 101 0 101 0 ------------------
config/kernel_linux_headers_sanitised.in | 62 0 62 0 -----------
config/ct-behave.in | 82 0 82 0 ---------------
config/kernel_linux.in | 134 0 134 0 ------------------------
config/global.in | 10 5 5 0 +-
config/download_extract.in | 171 0 171 0 -------------------------------
config/cc_gcc.in | 130 0 130 0 ------------------------
config/libc_glibc.in | 124 0 124 0 ----------------------
config/libc.in | 4 2 2 0
17 files changed, 15 insertions(+), 1273 deletions(-)
1.1 --- a/config/build-behave.in Thu Apr 17 20:02:07 2008 +0000
1.2 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000
1.3 @@ -1,45 +0,0 @@
1.4 -# Options related to how the build behaves
1.5 -
1.6 -comment "Build behavior"
1.7 -
1.8 -config PARALLEL_JOBS
1.9 - int
1.10 - prompt "Number of parallel jobs"
1.11 - default 1
1.12 - help
1.13 - Number of jobs make will be allowed to run concurently.
1.14 - Set this higher than the number of processors you have, but not too high.
1.15 - A good rule of thumb is twice the number of processors you have.
1.16 -
1.17 - Enter 1 (or 0) to have only one job at a time.
1.18 -
1.19 -config LOAD
1.20 - int
1.21 - prompt "Maximum allowed load"
1.22 - default 0
1.23 - help
1.24 - Specifies that no new jobs should be started if there are others jobs
1.25 - running and the load average is at least this value.
1.26 -
1.27 - Makes sense on SMP machines only.
1.28 -
1.29 - Enter 0 to have no limit on the load average.
1.30 -
1.31 - Note: only the integer part of the load is allowed here (you can't enter
1.32 - 0.75 for example).
1.33 -
1.34 -config NICE
1.35 - int
1.36 - prompt "Nice level"
1.37 - default 0
1.38 - range 0 19
1.39 - help
1.40 - Renices the build process up.
1.41 -
1.42 -config USE_PIPES
1.43 - bool
1.44 - prompt "Use -pipe"
1.45 - default y
1.46 - help
1.47 - Use gcc's option -pipe to use pipes rather than temp files when building
1.48 - the toolchain.
2.1 --- a/config/cc.in Thu Apr 17 20:02:07 2008 +0000
2.2 +++ b/config/cc.in Thu Apr 17 20:26:25 2008 +0000
2.3 @@ -32,7 +32,7 @@
2.4 default "gcc" if CC_GCC
2.5
2.6 if CC_GCC
2.7 -source config/cc_gcc.in
2.8 +source config/cc/cc_gcc.in
2.9 endif
2.10
2.11 config CC_SUPPORT_CXX
3.1 --- /dev/null Thu Jan 01 00:00:00 1970 +0000
3.2 +++ b/config/cc/cc_gcc.in Thu Apr 17 20:26:25 2008 +0000
3.3 @@ -0,0 +1,130 @@
3.4 +# Compiler options
3.5 +
3.6 +choice
3.7 + bool
3.8 + prompt "gcc version"
3.9 +
3.10 +config CC_V_2_95_3
3.11 + bool
3.12 + prompt "2.95.3 (OBSOLETE)"
3.13 + depends on OBSOLETE
3.14 +
3.15 +config CC_V_3_2_3
3.16 + bool
3.17 + prompt "3.2.3 (OBSOLETE)"
3.18 + depends on OBSOLETE
3.19 +
3.20 +config CC_V_3_3_6
3.21 + bool
3.22 + prompt "3.3.6 (OBSOLETE)"
3.23 + depends on OBSOLETE
3.24 +
3.25 +config CC_V_3_4_6
3.26 + bool
3.27 + prompt "3.4.6 (OBSOLETE)"
3.28 + depends on OBSOLETE
3.29 +
3.30 +config CC_V_4_0_0
3.31 + bool
3.32 + prompt "4.0.0 (OBSOLETE)"
3.33 + depends on OBSOLETE
3.34 +
3.35 +config CC_V_4_0_1
3.36 + bool
3.37 + prompt "4.0.1 (OBSOLETE)"
3.38 + depends on OBSOLETE
3.39 +
3.40 +config CC_V_4_0_2
3.41 + bool
3.42 + prompt "4.0.2 (OBSOLETE)"
3.43 + depends on OBSOLETE
3.44 +
3.45 +config CC_V_4_0_3
3.46 + bool
3.47 + prompt "4.0.3 (OBSOLETE)"
3.48 + depends on OBSOLETE
3.49 +
3.50 +config CC_V_4_0_4
3.51 + bool
3.52 + prompt "4.0.4"
3.53 +
3.54 +config CC_V_4_1_0
3.55 + bool
3.56 + prompt "4.1.0 (OBSOLETE)"
3.57 + depends on OBSOLETE
3.58 +
3.59 +config CC_V_4_1_1
3.60 + bool
3.61 + prompt "4.1.1 (OBSOLETE)"
3.62 + depends on OBSOLETE
3.63 +
3.64 +config CC_V_4_1_2
3.65 + bool
3.66 + prompt "4.1.2"
3.67 +
3.68 +config CC_V_4_2_0
3.69 + bool
3.70 + prompt "4.2.0"
3.71 +
3.72 +config CC_V_4_2_1
3.73 + bool
3.74 + prompt "4.2.1"
3.75 +
3.76 +config CC_V_4_2_2
3.77 + bool
3.78 + prompt "4.2.2"
3.79 +
3.80 +config CC_V_4_2_3
3.81 + bool
3.82 + prompt "4.2.3 (EXPERIMENTAL)"
3.83 + depends on EXPERIMENTAL
3.84 +
3.85 +# CT_INSERT_VERSION_ABOVE
3.86 +# Don't remove above line!
3.87 +endchoice
3.88 +
3.89 +config CC_VERSION
3.90 + string
3.91 + default "2.95.3" if CC_V_2_95_3
3.92 + default "3.2.3" if CC_V_3_2_3
3.93 + default "3.3.6" if CC_V_3_3_6
3.94 + default "3.4.6" if CC_V_3_4_6
3.95 + default "4.0.0" if CC_V_4_0_0
3.96 + default "4.0.1" if CC_V_4_0_1
3.97 + default "4.0.2" if CC_V_4_0_2
3.98 + default "4.0.3" if CC_V_4_0_3
3.99 + default "4.0.4" if CC_V_4_0_4
3.100 + default "4.1.0" if CC_V_4_1_0
3.101 + default "4.1.1" if CC_V_4_1_1
3.102 + default "4.1.2" if CC_V_4_1_2
3.103 + default "4.2.0" if CC_V_4_2_0
3.104 + default "4.2.1" if CC_V_4_2_1
3.105 + default "4.2.2" if CC_V_4_2_2
3.106 + default "4.2.3" if CC_V_4_2_3
3.107 +# CT_INSERT_VERSION_STRING_ABOVE
3.108 +# Don't remove above line!
3.109 +
3.110 +config CC_CXA_ATEXIT
3.111 + bool
3.112 + prompt "__cxa_atexit"
3.113 + default "y"
3.114 + help
3.115 + If you get the missing symbol "__cxa_atexit" when building C++ programs,
3.116 + you might want to try disabling this option.
3.117 +
3.118 +config CC_CORE_EXTRA_CONFIG
3.119 + string
3.120 + prompt "Core gcc extra config"
3.121 + default ""
3.122 + help
3.123 + Extra flags to pass onto ./configure when configuring the core gcc.
3.124 +
3.125 + The core gcc is a stripped down, C-only compiler needed to build
3.126 + the C library. Kinda bootstrap gcc, if you wish.
3.127 +
3.128 +config CC_EXTRA_CONFIG
3.129 + string
3.130 + prompt "gcc extra config"
3.131 + default ""
3.132 + help
3.133 + Extra flags to pass onto ./configure when configuring gcc.
4.1 --- a/config/cc_gcc.in Thu Apr 17 20:02:07 2008 +0000
4.2 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000
4.3 @@ -1,130 +0,0 @@
4.4 -# Compiler options
4.5 -
4.6 -choice
4.7 - bool
4.8 - prompt "gcc version"
4.9 -
4.10 -config CC_V_2_95_3
4.11 - bool
4.12 - prompt "2.95.3 (OBSOLETE)"
4.13 - depends on OBSOLETE
4.14 -
4.15 -config CC_V_3_2_3
4.16 - bool
4.17 - prompt "3.2.3 (OBSOLETE)"
4.18 - depends on OBSOLETE
4.19 -
4.20 -config CC_V_3_3_6
4.21 - bool
4.22 - prompt "3.3.6 (OBSOLETE)"
4.23 - depends on OBSOLETE
4.24 -
4.25 -config CC_V_3_4_6
4.26 - bool
4.27 - prompt "3.4.6 (OBSOLETE)"
4.28 - depends on OBSOLETE
4.29 -
4.30 -config CC_V_4_0_0
4.31 - bool
4.32 - prompt "4.0.0 (OBSOLETE)"
4.33 - depends on OBSOLETE
4.34 -
4.35 -config CC_V_4_0_1
4.36 - bool
4.37 - prompt "4.0.1 (OBSOLETE)"
4.38 - depends on OBSOLETE
4.39 -
4.40 -config CC_V_4_0_2
4.41 - bool
4.42 - prompt "4.0.2 (OBSOLETE)"
4.43 - depends on OBSOLETE
4.44 -
4.45 -config CC_V_4_0_3
4.46 - bool
4.47 - prompt "4.0.3 (OBSOLETE)"
4.48 - depends on OBSOLETE
4.49 -
4.50 -config CC_V_4_0_4
4.51 - bool
4.52 - prompt "4.0.4"
4.53 -
4.54 -config CC_V_4_1_0
4.55 - bool
4.56 - prompt "4.1.0 (OBSOLETE)"
4.57 - depends on OBSOLETE
4.58 -
4.59 -config CC_V_4_1_1
4.60 - bool
4.61 - prompt "4.1.1 (OBSOLETE)"
4.62 - depends on OBSOLETE
4.63 -
4.64 -config CC_V_4_1_2
4.65 - bool
4.66 - prompt "4.1.2"
4.67 -
4.68 -config CC_V_4_2_0
4.69 - bool
4.70 - prompt "4.2.0"
4.71 -
4.72 -config CC_V_4_2_1
4.73 - bool
4.74 - prompt "4.2.1"
4.75 -
4.76 -config CC_V_4_2_2
4.77 - bool
4.78 - prompt "4.2.2"
4.79 -
4.80 -config CC_V_4_2_3
4.81 - bool
4.82 - prompt "4.2.3 (EXPERIMENTAL)"
4.83 - depends on EXPERIMENTAL
4.84 -
4.85 -# CT_INSERT_VERSION_ABOVE
4.86 -# Don't remove above line!
4.87 -endchoice
4.88 -
4.89 -config CC_VERSION
4.90 - string
4.91 - default "2.95.3" if CC_V_2_95_3
4.92 - default "3.2.3" if CC_V_3_2_3
4.93 - default "3.3.6" if CC_V_3_3_6
4.94 - default "3.4.6" if CC_V_3_4_6
4.95 - default "4.0.0" if CC_V_4_0_0
4.96 - default "4.0.1" if CC_V_4_0_1
4.97 - default "4.0.2" if CC_V_4_0_2
4.98 - default "4.0.3" if CC_V_4_0_3
4.99 - default "4.0.4" if CC_V_4_0_4
4.100 - default "4.1.0" if CC_V_4_1_0
4.101 - default "4.1.1" if CC_V_4_1_1
4.102 - default "4.1.2" if CC_V_4_1_2
4.103 - default "4.2.0" if CC_V_4_2_0
4.104 - default "4.2.1" if CC_V_4_2_1
4.105 - default "4.2.2" if CC_V_4_2_2
4.106 - default "4.2.3" if CC_V_4_2_3
4.107 -# CT_INSERT_VERSION_STRING_ABOVE
4.108 -# Don't remove above line!
4.109 -
4.110 -config CC_CXA_ATEXIT
4.111 - bool
4.112 - prompt "__cxa_atexit"
4.113 - default "y"
4.114 - help
4.115 - If you get the missing symbol "__cxa_atexit" when building C++ programs,
4.116 - you might want to try disabling this option.
4.117 -
4.118 -config CC_CORE_EXTRA_CONFIG
4.119 - string
4.120 - prompt "Core gcc extra config"
4.121 - default ""
4.122 - help
4.123 - Extra flags to pass onto ./configure when configuring the core gcc.
4.124 -
4.125 - The core gcc is a stripped down, C-only compiler needed to build
4.126 - the C library. Kinda bootstrap gcc, if you wish.
4.127 -
4.128 -config CC_EXTRA_CONFIG
4.129 - string
4.130 - prompt "gcc extra config"
4.131 - default ""
4.132 - help
4.133 - Extra flags to pass onto ./configure when configuring gcc.
5.1 --- a/config/ct-behave.in Thu Apr 17 20:02:07 2008 +0000
5.2 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000
5.3 @@ -1,82 +0,0 @@
5.4 -# Options specific to crosstool-NG overall behavior
5.5 -
5.6 -comment "crosstool-NG behavior"
5.7 -
5.8 -config OBSOLETE
5.9 - bool
5.10 - prompt "Use obsolete features"
5.11 - default n
5.12 - help
5.13 - If you set this to Y, you will be able to select obsolete features.
5.14 -
5.15 - Such obsolete features are the use of old kernel headers, old
5.16 - gcc versions, etc...
5.17 -
5.18 -config EXPERIMENTAL
5.19 - bool
5.20 - prompt "Try features marked as EXPERIMENTAL"
5.21 - default n
5.22 - help
5.23 - If you set this to Y, then you will be able to try very experimental
5.24 - features.
5.25 -
5.26 - Experimental features can be one of:
5.27 - - working, in which case you should tell me it is!
5.28 - - buggy, in which case you could try patching and send me the result
5.29 - - unfinished, in which case you could try hacking it and send me the result
5.30 - - non-existant, in which case you could also try hacking it in and send me
5.31 - the result
5.32 -
5.33 -config BROKEN
5.34 - bool
5.35 - prompt "Try broken stuff"
5.36 - default n
5.37 - depends on EXPERIMENTAL
5.38 - help
5.39 - Select this if you want to _debug_ broken stuff.
5.40 -
5.41 -config DEBUG_CT
5.42 - bool
5.43 - prompt "Debug crosstool-NG"
5.44 - default n
5.45 - help
5.46 - Say 'y' here to get some debugging options
5.47 -
5.48 -if DEBUG_CT
5.49 -
5.50 -config DEBUG_CT_PAUSE_STEPS
5.51 - bool
5.52 - prompt "Pause between every steps"
5.53 - default n
5.54 - help
5.55 - Say 'y' if you intend to attend the build, and want to investigate
5.56 - the result of each steps before running the next one.
5.57 -
5.58 -config DEBUG_CT_SAVE_STEPS
5.59 - bool
5.60 - prompt "Save intermediate steps"
5.61 - default n
5.62 - help
5.63 - If you say 'y' here, then you will be able to restart crosstool-NG at
5.64 - any step.
5.65 -
5.66 - It is not currently possible to restart at any of the debug facility.
5.67 - They are treated as a whole.
5.68 -
5.69 - See docs/overview.txt for the list of steps.
5.70 -
5.71 -config DEBUG_CT_SAVE_STEPS_GZIP
5.72 - bool
5.73 - prompt "gzip saved states"
5.74 - default y
5.75 - depends on DEBUG_CT_SAVE_STEPS
5.76 - help
5.77 - If you are tight on space, then you can ask to gzip the saved states
5.78 - tarballs. On the other hand, this takes some longer time...
5.79 -
5.80 - To lose as less time as possible, the gzip process is done with a low
5.81 - compression ratio (-3), which gives roughly 70% gain in size. Going
5.82 - further doesn't gain much, and takes far more time (believe me, I've
5.83 - got figures here! :-) ).
5.84 -
5.85 -endif
6.1 --- a/config/download_extract.in Thu Apr 17 20:02:07 2008 +0000
6.2 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000
6.3 @@ -1,171 +0,0 @@
6.4 -# Options specific to downloading and extracting packages
6.5 -
6.6 -comment "Downloading"
6.7 -
6.8 -config FORCE_DOWNLOAD
6.9 - bool
6.10 - prompt "Force downloads"
6.11 - default n
6.12 - help
6.13 - Force downloading tarballs, even if one already exists.
6.14 -
6.15 - Usefull if you suspect a tarball to be damaged.
6.16 -
6.17 -config ONLY_DOWNLOAD
6.18 - bool
6.19 - prompt "Stop after downloading tarballs"
6.20 - default n
6.21 - help
6.22 - Only download the tarballs. Exit once it done.
6.23 -
6.24 - Usefull to pre-retrieve the tarballs before going off-line.
6.25 -
6.26 -choice
6.27 - bool
6.28 - prompt "Proxy type"
6.29 - default USE_NO_PROXY
6.30 -
6.31 -config PROXY_TYPE_NONE
6.32 - bool
6.33 - prompt "No proxy"
6.34 - help
6.35 - Select this option if you have a direct connection to the internet,
6.36 - or if you already set the environment adequately.
6.37 -
6.38 -config PROXY_TYPE_HTTP
6.39 - bool
6.40 - prompt "HTTP proxy"
6.41 - help
6.42 - Use an HTTP proxy to connect to to the internet.
6.43 - Only the http and ftp protocols will be tunneled through this
6.44 - proxy.
6.45 -
6.46 - Alternatively to setting this option, you can set and export the
6.47 - following variables in your environment:
6.48 - ftp_proxy=http://user:passwd@proxy.server:port/
6.49 - http_proxy=http://user:passwd@proxy.server:port/
6.50 - https_proxy=http://user:passwd@proxy.server:port/
6.51 -
6.52 -# Haha! Here is an interesting feature/bug of mconf!
6.53 -# The following config entries will be shown out-side the
6.54 -# choice menu!
6.55 -# To add a third entry in the choice menu, add it after the
6.56 -# if...endif conditional below, and so on for a fourth entry...
6.57 -if PROXY_TYPE_HTTP
6.58 -
6.59 -config PROXY_HOST
6.60 - string
6.61 - prompt "hostname/IP"
6.62 -
6.63 -config PROXY_PORT
6.64 - int
6.65 - prompt "port"
6.66 - default 0
6.67 -
6.68 -config PROXY_USER
6.69 - string
6.70 - prompt "user name"
6.71 -
6.72 -config PROXY_PASS
6.73 - string
6.74 - prompt "password"
6.75 -
6.76 -endif # USE_HTTP_PROXY
6.77 -
6.78 -config PROXY_TYPE_SOCKS
6.79 - bool
6.80 - prompt "SOCKS 4/5 proxy"
6.81 - help
6.82 - Use a Socks 4/5 proxy to connect to the internet.
6.83 - All protocols can get tunneled through this kind of proxy (depending
6.84 - on your proxy configuration, so;e do not allow all protocols, but
6.85 - chances are that protocols needed by crosstool-NG are allowed).
6.86 -
6.87 - Alternatively to setting this option, you can set and export the
6.88 - following variable in your environment:
6.89 - LD_PRELOAD=/path/to/your/tsocks-library.so
6.90 -
6.91 - In any case, wether you set this option or you export the aforementionned
6.92 - variable, you will _have_ to configure the /etc/tsocks.conf file
6.93 - accordingly to your network setup.
6.94 -
6.95 - This option makes use of the tsocks library. You will have to have tsocks
6.96 - installed on your system, of course.
6.97 -
6.98 - If you think you do not know what tsocks is, or how to configure it,
6.99 - chances are that you do not need to set this option.
6.100 -
6.101 -if PROXY_TYPE_SOCKS
6.102 -
6.103 -choice
6.104 - bool
6.105 - prompt "type"
6.106 - default PROXY_TYPE_SOCKS_5
6.107 -
6.108 -config PROXY_TYPE_SOCKS_5
6.109 - bool
6.110 - prompt "SOCKS 5"
6.111 -
6.112 -config PROXY_TYPE_SOCKS_4
6.113 - bool
6.114 - prompt "SOCKS 4"
6.115 -
6.116 -endchoice
6.117 -
6.118 -config PROXY_HOST
6.119 - string
6.120 - prompt "hostname/IP"
6.121 -
6.122 -config PROXY_PORT
6.123 - int
6.124 - prompt "port"
6.125 - default 0
6.126 -
6.127 -config PROXY_USER
6.128 - string
6.129 - prompt "user name"
6.130 -
6.131 -config PROXY_PASS
6.132 - string
6.133 - prompt "password"
6.134 -
6.135 -endif # USE_SOCKS_PROXY
6.136 -
6.137 -endchoice
6.138 -
6.139 -config PROXY_TYPE
6.140 - string
6.141 - default "none" if PROXY_TYPE_NONE
6.142 - default "HTTP" if PROXY_TYPE_HTTP
6.143 - default "socks5" if PROXY_TYPE_SOCKS_5
6.144 - default "socks4" if PROXY_TYPE_SOCKS_4
6.145 -
6.146 -# Force restore indentation
6.147 -config BREAK_INDENT
6.148 - bool
6.149 - default n
6.150 -
6.151 -if ! ONLY_DOWNLOAD
6.152 -
6.153 -comment "Extracting"
6.154 -
6.155 -config FORCE_EXTRACT
6.156 - bool
6.157 - prompt "Force extractions"
6.158 - default n
6.159 - help
6.160 - Force extraction of already exctracted tarballs.
6.161 -
6.162 - Usefull if you suspect a previous extract did not complete (eg. broken
6.163 - tarball), or you added a new set of patches for this component.
6.164 -
6.165 -config ONLY_EXTRACT
6.166 - bool
6.167 - prompt "Stop after extracting tarballs"
6.168 - default n
6.169 - help
6.170 - Exit after unpacking and patching tarballs.
6.171 -
6.172 - Usefull to look at the code before doing the build itself.
6.173 -
6.174 -endif # ! ONLY_DOWNLOAD
7.1 --- a/config/global.in Thu Apr 17 20:02:07 2008 +0000
7.2 +++ b/config/global.in Thu Apr 17 20:26:25 2008 +0000
7.3 @@ -2,10 +2,10 @@
7.4
7.5 menu "Paths and misc options"
7.6
7.7 -source "config/ct-behave.in"
7.8 -source "config/download_extract.in"
7.9 -source "config/build-behave.in"
7.10 -source "config/paths.in"
7.11 -source "config/logging.in"
7.12 +source "config/global/ct-behave.in"
7.13 +source "config/global/download_extract.in"
7.14 +source "config/global/build-behave.in"
7.15 +source "config/global/paths.in"
7.16 +source "config/global/logging.in"
7.17
7.18 endmenu
8.1 --- /dev/null Thu Jan 01 00:00:00 1970 +0000
8.2 +++ b/config/global/build-behave.in Thu Apr 17 20:26:25 2008 +0000
8.3 @@ -0,0 +1,45 @@
8.4 +# Options related to how the build behaves
8.5 +
8.6 +comment "Build behavior"
8.7 +
8.8 +config PARALLEL_JOBS
8.9 + int
8.10 + prompt "Number of parallel jobs"
8.11 + default 1
8.12 + help
8.13 + Number of jobs make will be allowed to run concurently.
8.14 + Set this higher than the number of processors you have, but not too high.
8.15 + A good rule of thumb is twice the number of processors you have.
8.16 +
8.17 + Enter 1 (or 0) to have only one job at a time.
8.18 +
8.19 +config LOAD
8.20 + int
8.21 + prompt "Maximum allowed load"
8.22 + default 0
8.23 + help
8.24 + Specifies that no new jobs should be started if there are others jobs
8.25 + running and the load average is at least this value.
8.26 +
8.27 + Makes sense on SMP machines only.
8.28 +
8.29 + Enter 0 to have no limit on the load average.
8.30 +
8.31 + Note: only the integer part of the load is allowed here (you can't enter
8.32 + 0.75 for example).
8.33 +
8.34 +config NICE
8.35 + int
8.36 + prompt "Nice level"
8.37 + default 0
8.38 + range 0 19
8.39 + help
8.40 + Renices the build process up.
8.41 +
8.42 +config USE_PIPES
8.43 + bool
8.44 + prompt "Use -pipe"
8.45 + default y
8.46 + help
8.47 + Use gcc's option -pipe to use pipes rather than temp files when building
8.48 + the toolchain.
9.1 --- /dev/null Thu Jan 01 00:00:00 1970 +0000
9.2 +++ b/config/global/ct-behave.in Thu Apr 17 20:26:25 2008 +0000
9.3 @@ -0,0 +1,82 @@
9.4 +# Options specific to crosstool-NG overall behavior
9.5 +
9.6 +comment "crosstool-NG behavior"
9.7 +
9.8 +config OBSOLETE
9.9 + bool
9.10 + prompt "Use obsolete features"
9.11 + default n
9.12 + help
9.13 + If you set this to Y, you will be able to select obsolete features.
9.14 +
9.15 + Such obsolete features are the use of old kernel headers, old
9.16 + gcc versions, etc...
9.17 +
9.18 +config EXPERIMENTAL
9.19 + bool
9.20 + prompt "Try features marked as EXPERIMENTAL"
9.21 + default n
9.22 + help
9.23 + If you set this to Y, then you will be able to try very experimental
9.24 + features.
9.25 +
9.26 + Experimental features can be one of:
9.27 + - working, in which case you should tell me it is!
9.28 + - buggy, in which case you could try patching and send me the result
9.29 + - unfinished, in which case you could try hacking it and send me the result
9.30 + - non-existant, in which case you could also try hacking it in and send me
9.31 + the result
9.32 +
9.33 +config BROKEN
9.34 + bool
9.35 + prompt "Try broken stuff"
9.36 + default n
9.37 + depends on EXPERIMENTAL
9.38 + help
9.39 + Select this if you want to _debug_ broken stuff.
9.40 +
9.41 +config DEBUG_CT
9.42 + bool
9.43 + prompt "Debug crosstool-NG"
9.44 + default n
9.45 + help
9.46 + Say 'y' here to get some debugging options
9.47 +
9.48 +if DEBUG_CT
9.49 +
9.50 +config DEBUG_CT_PAUSE_STEPS
9.51 + bool
9.52 + prompt "Pause between every steps"
9.53 + default n
9.54 + help
9.55 + Say 'y' if you intend to attend the build, and want to investigate
9.56 + the result of each steps before running the next one.
9.57 +
9.58 +config DEBUG_CT_SAVE_STEPS
9.59 + bool
9.60 + prompt "Save intermediate steps"
9.61 + default n
9.62 + help
9.63 + If you say 'y' here, then you will be able to restart crosstool-NG at
9.64 + any step.
9.65 +
9.66 + It is not currently possible to restart at any of the debug facility.
9.67 + They are treated as a whole.
9.68 +
9.69 + See docs/overview.txt for the list of steps.
9.70 +
9.71 +config DEBUG_CT_SAVE_STEPS_GZIP
9.72 + bool
9.73 + prompt "gzip saved states"
9.74 + default y
9.75 + depends on DEBUG_CT_SAVE_STEPS
9.76 + help
9.77 + If you are tight on space, then you can ask to gzip the saved states
9.78 + tarballs. On the other hand, this takes some longer time...
9.79 +
9.80 + To lose as less time as possible, the gzip process is done with a low
9.81 + compression ratio (-3), which gives roughly 70% gain in size. Going
9.82 + further doesn't gain much, and takes far more time (believe me, I've
9.83 + got figures here! :-) ).
9.84 +
9.85 +endif
10.1 --- /dev/null Thu Jan 01 00:00:00 1970 +0000
10.2 +++ b/config/global/download_extract.in Thu Apr 17 20:26:25 2008 +0000
10.3 @@ -0,0 +1,171 @@
10.4 +# Options specific to downloading and extracting packages
10.5 +
10.6 +comment "Downloading"
10.7 +
10.8 +config FORCE_DOWNLOAD
10.9 + bool
10.10 + prompt "Force downloads"
10.11 + default n
10.12 + help
10.13 + Force downloading tarballs, even if one already exists.
10.14 +
10.15 + Usefull if you suspect a tarball to be damaged.
10.16 +
10.17 +config ONLY_DOWNLOAD
10.18 + bool
10.19 + prompt "Stop after downloading tarballs"
10.20 + default n
10.21 + help
10.22 + Only download the tarballs. Exit once it done.
10.23 +
10.24 + Usefull to pre-retrieve the tarballs before going off-line.
10.25 +
10.26 +choice
10.27 + bool
10.28 + prompt "Proxy type"
10.29 + default USE_NO_PROXY
10.30 +
10.31 +config PROXY_TYPE_NONE
10.32 + bool
10.33 + prompt "No proxy"
10.34 + help
10.35 + Select this option if you have a direct connection to the internet,
10.36 + or if you already set the environment adequately.
10.37 +
10.38 +config PROXY_TYPE_HTTP
10.39 + bool
10.40 + prompt "HTTP proxy"
10.41 + help
10.42 + Use an HTTP proxy to connect to to the internet.
10.43 + Only the http and ftp protocols will be tunneled through this
10.44 + proxy.
10.45 +
10.46 + Alternatively to setting this option, you can set and export the
10.47 + following variables in your environment:
10.48 + ftp_proxy=http://user:passwd@proxy.server:port/
10.49 + http_proxy=http://user:passwd@proxy.server:port/
10.50 + https_proxy=http://user:passwd@proxy.server:port/
10.51 +
10.52 +# Haha! Here is an interesting feature/bug of mconf!
10.53 +# The following config entries will be shown out-side the
10.54 +# choice menu!
10.55 +# To add a third entry in the choice menu, add it after the
10.56 +# if...endif conditional below, and so on for a fourth entry...
10.57 +if PROXY_TYPE_HTTP
10.58 +
10.59 +config PROXY_HOST
10.60 + string
10.61 + prompt "hostname/IP"
10.62 +
10.63 +config PROXY_PORT
10.64 + int
10.65 + prompt "port"
10.66 + default 0
10.67 +
10.68 +config PROXY_USER
10.69 + string
10.70 + prompt "user name"
10.71 +
10.72 +config PROXY_PASS
10.73 + string
10.74 + prompt "password"
10.75 +
10.76 +endif # USE_HTTP_PROXY
10.77 +
10.78 +config PROXY_TYPE_SOCKS
10.79 + bool
10.80 + prompt "SOCKS 4/5 proxy"
10.81 + help
10.82 + Use a Socks 4/5 proxy to connect to the internet.
10.83 + All protocols can get tunneled through this kind of proxy (depending
10.84 + on your proxy configuration, so;e do not allow all protocols, but
10.85 + chances are that protocols needed by crosstool-NG are allowed).
10.86 +
10.87 + Alternatively to setting this option, you can set and export the
10.88 + following variable in your environment:
10.89 + LD_PRELOAD=/path/to/your/tsocks-library.so
10.90 +
10.91 + In any case, wether you set this option or you export the aforementionned
10.92 + variable, you will _have_ to configure the /etc/tsocks.conf file
10.93 + accordingly to your network setup.
10.94 +
10.95 + This option makes use of the tsocks library. You will have to have tsocks
10.96 + installed on your system, of course.
10.97 +
10.98 + If you think you do not know what tsocks is, or how to configure it,
10.99 + chances are that you do not need to set this option.
10.100 +
10.101 +if PROXY_TYPE_SOCKS
10.102 +
10.103 +choice
10.104 + bool
10.105 + prompt "type"
10.106 + default PROXY_TYPE_SOCKS_5
10.107 +
10.108 +config PROXY_TYPE_SOCKS_5
10.109 + bool
10.110 + prompt "SOCKS 5"
10.111 +
10.112 +config PROXY_TYPE_SOCKS_4
10.113 + bool
10.114 + prompt "SOCKS 4"
10.115 +
10.116 +endchoice
10.117 +
10.118 +config PROXY_HOST
10.119 + string
10.120 + prompt "hostname/IP"
10.121 +
10.122 +config PROXY_PORT
10.123 + int
10.124 + prompt "port"
10.125 + default 0
10.126 +
10.127 +config PROXY_USER
10.128 + string
10.129 + prompt "user name"
10.130 +
10.131 +config PROXY_PASS
10.132 + string
10.133 + prompt "password"
10.134 +
10.135 +endif # USE_SOCKS_PROXY
10.136 +
10.137 +endchoice
10.138 +
10.139 +config PROXY_TYPE
10.140 + string
10.141 + default "none" if PROXY_TYPE_NONE
10.142 + default "HTTP" if PROXY_TYPE_HTTP
10.143 + default "socks5" if PROXY_TYPE_SOCKS_5
10.144 + default "socks4" if PROXY_TYPE_SOCKS_4
10.145 +
10.146 +# Force restore indentation
10.147 +config BREAK_INDENT
10.148 + bool
10.149 + default n
10.150 +
10.151 +if ! ONLY_DOWNLOAD
10.152 +
10.153 +comment "Extracting"
10.154 +
10.155 +config FORCE_EXTRACT
10.156 + bool
10.157 + prompt "Force extractions"
10.158 + default n
10.159 + help
10.160 + Force extraction of already exctracted tarballs.
10.161 +
10.162 + Usefull if you suspect a previous extract did not complete (eg. broken
10.163 + tarball), or you added a new set of patches for this component.
10.164 +
10.165 +config ONLY_EXTRACT
10.166 + bool
10.167 + prompt "Stop after extracting tarballs"
10.168 + default n
10.169 + help
10.170 + Exit after unpacking and patching tarballs.
10.171 +
10.172 + Usefull to look at the code before doing the build itself.
10.173 +
10.174 +endif # ! ONLY_DOWNLOAD
11.1 --- /dev/null Thu Jan 01 00:00:00 1970 +0000
11.2 +++ b/config/global/logging.in Thu Apr 17 20:26:25 2008 +0000
11.3 @@ -0,0 +1,110 @@
11.4 +# Options specific to logging
11.5 +
11.6 +comment "Logging"
11.7 +
11.8 +choice
11.9 + bool
11.10 + prompt "Maximum log level to see:"
11.11 + default LOG_INFO if !DEBUG_CT
11.12 + default LOG_DEBUG if DEBUG_CT
11.13 +
11.14 +config LOG_ERROR
11.15 + bool
11.16 + prompt "ERROR"
11.17 + help
11.18 + The build will be silent.
11.19 + Only if there is an error will you see a message.
11.20 +
11.21 +config LOG_WARN
11.22 + bool
11.23 + prompt "WARN"
11.24 + help
11.25 + The same as above, plus warnings.
11.26 +
11.27 +config LOG_INFO
11.28 + bool
11.29 + prompt "INFO"
11.30 + help
11.31 + The same as above, plus informational messages (main steps).
11.32 +
11.33 +config LOG_EXTRA
11.34 + bool
11.35 + prompt "EXTRA"
11.36 + help
11.37 + The same as above, plus extra messages (sub-steps).
11.38 +
11.39 +config LOG_DEBUG
11.40 + bool
11.41 + prompt "DEBUG"
11.42 + help
11.43 + The same as above, plus lots of crosstool-NG debug information.
11.44 +
11.45 +config LOG_ALL
11.46 + bool
11.47 + prompt "ALL"
11.48 + help
11.49 + The same as above, plus all components build messages (very noisy!).
11.50 +
11.51 +endchoice
11.52 +
11.53 +config LOG_LEVEL_MAX
11.54 + string
11.55 + default "ERROR" if LOG_ERROR
11.56 + default "WARN" if LOG_WARN
11.57 + default "INFO" if LOG_INFO
11.58 + default "EXTRA" if LOG_EXTRA
11.59 + default "DEBUG" if LOG_DEBUG
11.60 + default "ALL" if LOG_ALL
11.61 +
11.62 +config LOG_SEE_TOOLS_WARN
11.63 + bool
11.64 + prompt "Warnings from the tools' builds"
11.65 + default n
11.66 + depends on ! LOG_ERROR
11.67 + help
11.68 + Treat warnings from the different tools as crosstool-NG warnings.
11.69 + If you say 'y' here, then those warnings will be prefixed with
11.70 + '[WARN ]' instead of the default '[ALL ]'.
11.71 +
11.72 + You can safely say 'n' here. Those warnings will anyway be
11.73 + recorded in the log file (provided you configured one).
11.74 +
11.75 + Tools error will always be logged as crosstool-NG errors.
11.76 +
11.77 +config LOG_PROGRESS_BAR
11.78 + bool
11.79 + prompt "Progress bar"
11.80 + default y
11.81 + depends on ! LOG_ALL
11.82 + help
11.83 + If you say 'y' here, you'll be able to see the elapsed time.
11.84 +
11.85 + As a bonus, you'll also get a rotating bar (/-\|) showing you
11.86 + that the build is not stalled (the bar rotates 1/4 every 10 lines
11.87 + of components build log).
11.88 +
11.89 + Note that the elapsed time can stall for a little while if a
11.90 + component has long commands, as the elapsed time is only updated
11.91 + each line.
11.92 +
11.93 +config LOG_TO_FILE
11.94 + bool
11.95 + prompt "Log to a file"
11.96 + default y
11.97 + help
11.98 + Save *full* logs to a file. Even log levels you didn't specify above
11.99 + will be available in this file. The log file will be named build.log
11.100 + and stored in the toolchain prefix dir (set above).
11.101 +
11.102 + As a bonus, there is a script in tools/extractConfig.sh that is able
11.103 + to extract the configuration of crosstool-NG from the log file.
11.104 +
11.105 + Definitely, say Y.
11.106 +
11.107 +config LOG_FILE_COMPRESS
11.108 + bool
11.109 + prompt "Compress the log file"
11.110 + default n
11.111 + depends on LOG_TO_FILE
11.112 + help
11.113 + Compress the log file once the toolchain is successfully built.
12.1 --- /dev/null Thu Jan 01 00:00:00 1970 +0000
12.2 +++ b/config/global/paths.in Thu Apr 17 20:26:25 2008 +0000
12.3 @@ -0,0 +1,89 @@
12.4 +# Options related to paths and install
12.5 +
12.6 +comment "Paths"
12.7 +
12.8 +config LOCAL_TARBALLS_DIR
12.9 + string
12.10 + prompt "Local tarballs directory"
12.11 + default ""
12.12 + help
12.13 + If you have previously downloaded the tarballs, enter the PATH where
12.14 + you stored them here.
12.15 +
12.16 +config SAVE_TARBALLS
12.17 + bool
12.18 + prompt "Save new tarballs"
12.19 + default n
12.20 + depends on LOCAL_TARBALLS_DIR != ""
12.21 + help
12.22 + If you say 'y' here, new downloaded tarballs will be saved in the
12.23 + directory you entered above.
12.24 +
12.25 +config PREFIX_DIR
12.26 + string
12.27 + prompt "Prefix directory"
12.28 + default "${HOME}/${CT_TARGET}"
12.29 + help
12.30 + This is the path the toolchain will run from.
12.31 +
12.32 +config INSTALL_DIR
12.33 + string
12.34 +# prompt "Install directory"
12.35 + default "${CT_PREFIX_DIR}"
12.36 +# help
12.37 +# This is the path the target will be installed into.
12.38 +#
12.39 +# Normally, you would set this to ${CT_PREFIX_DIR}, but if for some reasons
12.40 +# you can't write there, you can install somewhere else and have a third
12.41 +# person do the install for you.
12.42 +# The reason you might also want to install elsewhere is if you are going
12.43 +# to package your shinny new toolchain for distribution.
12.44 +
12.45 +config CUSTOM_PATCH
12.46 + bool
12.47 + prompt "Use custom patch directory"
12.48 + default n
12.49 + help
12.50 + If you have custom patches that you want to be applied, say 'Y' here and
12.51 + enter the path directory below.
12.52 +
12.53 + Note that you must ensure that the patch directory is arranged the same
12.54 + way the official directory is.
12.55 +
12.56 +config CUSTOM_PATCH_ONLY
12.57 + bool
12.58 + prompt "Only use custom patches"
12.59 + default n
12.60 + depends on CUSTOM_PATCH
12.61 + help
12.62 + Don't apply patches coming with crosstool-NG, only those patches available
12.63 + in the directory below.
12.64 +
12.65 + If you say 'N' here, then the patches provided with crosstool-NG will be
12.66 + applied first, and then your patches.
12.67 +
12.68 +config CUSTOM_PATCH_DIR
12.69 + string
12.70 + prompt "Custom patch directory"
12.71 + default ""
12.72 + depends on CUSTOM_PATCH
12.73 + help
12.74 + Enter the custom patch directory here.
12.75 +
12.76 +config REMOVE_DOCS
12.77 + bool
12.78 + prompt "Remove documentation"
12.79 + default n
12.80 + help
12.81 + Remove the installed documentation (man and info pages).
12.82 + Gains around 8MiB for a uClibc-based, C and C++ compiler.
12.83 +
12.84 +config INSTALL_DIR_RO
12.85 + bool
12.86 + prompt "Render the toolchain read-only"
12.87 + default n
12.88 + help
12.89 + Render the directory of the toolchain (and its sub-directories)
12.90 + read-only.
12.91 +
12.92 + Usefull for toolchains destined for production.
13.1 --- a/config/kernel.in Thu Apr 17 20:02:07 2008 +0000
13.2 +++ b/config/kernel.in Thu Apr 17 20:26:25 2008 +0000
13.3 @@ -19,7 +19,7 @@
13.4 string
13.5
13.6 if KERNEL_LINUX
13.7 -source config/kernel_linux.in
13.8 +source config/kernel/kernel_linux.in
13.9 endif
13.10
13.11 endmenu
14.1 --- /dev/null Thu Jan 01 00:00:00 1970 +0000
14.2 +++ b/config/kernel/kernel_linux.in Thu Apr 17 20:26:25 2008 +0000
14.3 @@ -0,0 +1,134 @@
14.4 +# Linux kernel options
14.5 +
14.6 +choice
14.7 + bool
14.8 + prompt "Get kernel headers from:"
14.9 +
14.10 +config KERNEL_LINUX_HEADERS_INSTALL
14.11 + bool
14.12 + prompt "kernel's 'headers_install'"
14.13 + help
14.14 + This will make use of the new headers_install rule in recent kernels.
14.15 + This is most probably what you want to use.
14.16 +
14.17 +config KERNEL_LINUX_HEADERS_SANITISED
14.18 + bool
14.19 + prompt "Mazur's sanitized headers (OBSOLETE)"
14.20 + depends on OBSOLETE
14.21 + select KERNEL_LINUX_NEEDS_CONFIG
14.22 + help
14.23 + M. Mazur used to maintain a tree of sanitised headers, but it is now
14.24 + obsoleted by the headers_install rule (above), and has not seen any
14.25 + update since 2.6.12
14.26 +
14.27 +config KERNEL_LINUX_HEADERS_COPY
14.28 + bool
14.29 + prompt "pure kernel headers (REALLY OBSOLETE)"
14.30 + depends on OBSOLETE
14.31 + select KERNEL_LINUX_NEEDS_CONFIG
14.32 + help
14.33 + This will simply copy the kernel headers to the toolchain.
14.34 +
14.35 + You do NOT want this. It's badly broken because it leaks kernel internals
14.36 + to userspace.
14.37 +
14.38 +config KERNEL_LINUX_HEADERS_USE_CUSTOM_DIR
14.39 + bool
14.40 + prompt "Use custom directory"
14.41 + help
14.42 + If you have some kernel headers lying around, you can enter the path
14.43 + below.
14.44 +
14.45 +endchoice
14.46 +
14.47 +config KERNEL
14.48 + string
14.49 + default "linux" if ! KERNEL_LINUX_HEADERS_SANITISED
14.50 + default "linux-libc-headers" if KERNEL_LINUX_HEADERS_SANITISED
14.51 +
14.52 +config KERNEL_VERSION_SEE_EXTRAVERSION
14.53 + bool
14.54 + prompt "See extra versions"
14.55 + default n
14.56 + depends on KERNEL_LINUX_HEADERS_COPY || KERNEL_LINUX_HEADERS_INSTALL
14.57 + help
14.58 + See extra versions (kernel with 4 numbers, eg 2.6.19.1).
14.59 +
14.60 + If you say 'no', you'll only see sub-level, 3-digit versions.
14.61 + If you say 'yes', you'll see far more versions!
14.62 +
14.63 + It is recommended that you say 'no', unless you _*know*_
14.64 + that an extra version fixes a headers bug.
14.65 +
14.66 +if KERNEL_LINUX_HEADERS_INSTALL
14.67 +source config/kernel/kernel_linux_headers_install.in
14.68 +endif
14.69 +
14.70 +if KERNEL_LINUX_HEADERS_COPY
14.71 +source config/kernel/kernel_linux_headers_copy.in
14.72 +endif
14.73 +
14.74 +if KERNEL_LINUX_HEADERS_SANITISED
14.75 +source config/kernel/kernel_linux_headers_sanitised.in
14.76 +endif
14.77 +
14.78 +config KERNEL_LINUX_HEADERS_CUSTOM_DIR
14.79 + string
14.80 + prompt "Where are those custom headers?"
14.81 + depends on KERNEL_LINUX_HEADERS_USE_CUSTOM_DIR
14.82 + help
14.83 + Enter the base directory where the headers are to be found.
14.84 +
14.85 + Eg. if the headers are in /some/place/include, then enter /some/place.
14.86 + This is the same path you entered when you typed:
14.87 + make INSTALL_HDR_PATH=/some/place headers_install
14.88 +
14.89 +if ! KERNEL_LINUX_HEADERS_USE_CUSTOM_DIR
14.90 +
14.91 +choice
14.92 + bool
14.93 + prompt "Kernel verbosity:"
14.94 + default KERNEL_LINUX_VERBOSITY_0
14.95 +
14.96 +config KERNEL_LINUX_VERBOSITY_0
14.97 + bool
14.98 + prompt "Simplified"
14.99 + help
14.100 + Print simplified command lines.
14.101 +
14.102 +config KERNEL_LINUX_VERBOSITY_1
14.103 + bool
14.104 + prompt "Full commands"
14.105 + help
14.106 + Print full command lines.
14.107 +
14.108 +config KERNEL_LINUX_VERBOSITY_2
14.109 + bool
14.110 + prompt "Exec reasons"
14.111 + help
14.112 + Print the reasons why a make target is rebuild.
14.113 +
14.114 +endchoice
14.115 +
14.116 +config KERNEL_LINUX_VERBOSE_LEVEL
14.117 + int
14.118 + default 0 if KERNEL_LINUX_VERBOSITY_0
14.119 + default 1 if KERNEL_LINUX_VERBOSITY_1
14.120 + default 2 if KERNEL_LINUX_VERBOSITY_2
14.121 +
14.122 +config KERNEL_LINUX_NEEDS_CONFIG
14.123 + bool
14.124 + default n
14.125 +
14.126 +config KERNEL_LINUX_CONFIG_FILE
14.127 + string
14.128 + prompt "Configuration file"
14.129 + depends on KERNEL_LINUX_NEEDS_CONFIG
14.130 + default ""
14.131 + help
14.132 + Path to a kernel configuration file.
14.133 +
14.134 + If you don't provide one, then the default configuration for
14.135 + your target will be used.
14.136 +
14.137 +endif
15.1 --- /dev/null Thu Jan 01 00:00:00 1970 +0000
15.2 +++ b/config/kernel/kernel_linux_headers_copy.in Thu Apr 17 20:26:25 2008 +0000
15.3 @@ -0,0 +1,42 @@
15.4 +choice
15.5 + bool
15.6 + prompt "Linux kernel version"
15.7 +
15.8 +config KERNEL_COPY_V_2_4_26
15.9 + bool
15.10 + prompt "2.4.26"
15.11 +
15.12 +config KERNEL_COPY_V_2_6_5
15.13 + bool
15.14 + prompt "2.6.5"
15.15 +
15.16 +config KERNEL_COPY_V_2_6_6
15.17 + bool
15.18 + prompt "2.6.6"
15.19 +
15.20 +config KERNEL_COPY_V_2_6_7
15.21 + bool
15.22 + prompt "2.6.7"
15.23 +
15.24 +config KERNEL_COPY_V_2_6_8
15.25 + bool
15.26 + prompt "2.6.8"
15.27 +
15.28 +config KERNEL_COPY_V_2_6_11_3
15.29 + bool
15.30 + prompt "2.6.11.3"
15.31 + depends on KERNEL_VERSION_SEE_EXTRAVERSION
15.32 +
15.33 +# CT_INSERT_VERSION_ABOVE
15.34 +# Don't remove above line!
15.35 +endchoice
15.36 +
15.37 +config KERNEL_VERSION
15.38 + string
15.39 + default "2.6.5" if KERNEL_COPY_V_2_6_5
15.40 + default "2.6.6" if KERNEL_COPY_V_2_6_6
15.41 + default "2.6.7" if KERNEL_COPY_V_2_6_7
15.42 + default "2.6.8" if KERNEL_COPY_V_2_6_8
15.43 + default "2.6.11.3" if KERNEL_COPY_V_2_6_11_3
15.44 +# CT_INSERT_VERSION_STRING_ABOVE
15.45 +# Don't remove above line!
16.1 --- /dev/null Thu Jan 01 00:00:00 1970 +0000
16.2 +++ b/config/kernel/kernel_linux_headers_install.in Thu Apr 17 20:26:25 2008 +0000
16.3 @@ -0,0 +1,168 @@
16.4 +choice
16.5 + bool
16.6 + prompt "Linux kernel version"
16.7 +
16.8 +config KERNEL_INSTALL_V_2_6_18_8
16.9 + bool
16.10 + prompt "2.6.18.8 (OBSOLETE)"
16.11 + depends on KERNEL_VERSION_SEE_EXTRAVERSION && OBSOLETE
16.12 +
16.13 +config KERNEL_INSTALL_V_2_6_19_7
16.14 + bool
16.15 + prompt "2.6.19.7 (OBSOLETE)"
16.16 + depends on KERNEL_VERSION_SEE_EXTRAVERSION && OBSOLETE
16.17 +
16.18 +config KERNEL_INSTALL_V_2_6_20_21
16.19 + bool
16.20 + prompt "2.6.20.21 (OBSOLETE)"
16.21 + depends on KERNEL_VERSION_SEE_EXTRAVERSION && OBSOLETE
16.22 +
16.23 +config KERNEL_INSTALL_V_2_6_21_7
16.24 + bool
16.25 + prompt "2.6.21.7 (OBSOLETE)"
16.26 + depends on KERNEL_VERSION_SEE_EXTRAVERSION && OBSOLETE
16.27 +
16.28 +config KERNEL_INSTALL_V_2_6_22_18
16.29 + bool
16.30 + prompt "2.6.22.18"
16.31 + depends on KERNEL_VERSION_SEE_EXTRAVERSION
16.32 +
16.33 +config KERNEL_INSTALL_V_2_6_23
16.34 + bool
16.35 + prompt "2.6.23"
16.36 +
16.37 +config KERNEL_INSTALL_V_2_6_23_1
16.38 + bool
16.39 + prompt "2.6.23.1"
16.40 + depends on KERNEL_VERSION_SEE_EXTRAVERSION
16.41 +
16.42 +config KERNEL_INSTALL_V_2_6_23_2
16.43 + bool
16.44 + prompt "2.6.23.2"
16.45 + depends on KERNEL_VERSION_SEE_EXTRAVERSION
16.46 +
16.47 +config KERNEL_INSTALL_V_2_6_23_3
16.48 + bool
16.49 + prompt "2.6.23.3"
16.50 + depends on KERNEL_VERSION_SEE_EXTRAVERSION
16.51 +
16.52 +config KERNEL_INSTALL_V_2_6_23_4
16.53 + bool
16.54 + prompt "2.6.23.4"
16.55 + depends on KERNEL_VERSION_SEE_EXTRAVERSION
16.56 +
16.57 +config KERNEL_INSTALL_V_2_6_23_5
16.58 + bool
16.59 + prompt "2.6.23.5"
16.60 + depends on KERNEL_VERSION_SEE_EXTRAVERSION
16.61 +
16.62 +config KERNEL_INSTALL_V_2_6_23_6
16.63 + bool
16.64 + prompt "2.6.23.6"
16.65 + depends on KERNEL_VERSION_SEE_EXTRAVERSION
16.66 +
16.67 +config KERNEL_INSTALL_V_2_6_23_7
16.68 + bool
16.69 + prompt "2.6.23.7"
16.70 + depends on KERNEL_VERSION_SEE_EXTRAVERSION
16.71 +
16.72 +config KERNEL_INSTALL_V_2_6_23_8
16.73 + bool
16.74 + prompt "2.6.23.8"
16.75 + depends on KERNEL_VERSION_SEE_EXTRAVERSION
16.76 +
16.77 +config KERNEL_INSTALL_V_2_6_23_9
16.78 + bool
16.79 + prompt "2.6.23.9"
16.80 + depends on KERNEL_VERSION_SEE_EXTRAVERSION
16.81 +
16.82 +config KERNEL_INSTALL_V_2_6_23_10
16.83 + bool
16.84 + prompt "2.6.23.10"
16.85 + depends on KERNEL_VERSION_SEE_EXTRAVERSION
16.86 +
16.87 +config KERNEL_INSTALL_V_2_6_23_11
16.88 + bool
16.89 + prompt "2.6.23.11"
16.90 + depends on KERNEL_VERSION_SEE_EXTRAVERSION
16.91 +
16.92 +config KERNEL_INSTALL_V_2_6_23_12
16.93 + bool
16.94 + prompt "2.6.23.12"
16.95 + depends on KERNEL_VERSION_SEE_EXTRAVERSION
16.96 +
16.97 +config KERNEL_INSTALL_V_2_6_23_13
16.98 + bool
16.99 + prompt "2.6.23.13"
16.100 + depends on KERNEL_VERSION_SEE_EXTRAVERSION
16.101 +
16.102 +config KERNEL_INSTALL_V_2_6_23_14
16.103 + bool
16.104 + prompt "2.6.23.14"
16.105 + depends on KERNEL_VERSION_SEE_EXTRAVERSION
16.106 +
16.107 +config KERNEL_INSTALL_V_2_6_23_15
16.108 + bool
16.109 + prompt "2.6.23.15"
16.110 + depends on KERNEL_VERSION_SEE_EXTRAVERSION
16.111 +
16.112 +config KERNEL_INSTALL_V_2_6_23_16
16.113 + bool
16.114 + prompt "2.6.23.16"
16.115 + depends on KERNEL_VERSION_SEE_EXTRAVERSION
16.116 +
16.117 +config KERNEL_INSTALL_V_2_6_24
16.118 + bool
16.119 + prompt "2.6.24"
16.120 +
16.121 +config KERNEL_INSTALL_V_2_6_24_1
16.122 + bool
16.123 + prompt "2.6.24.1"
16.124 + depends on KERNEL_VERSION_SEE_EXTRAVERSION
16.125 +
16.126 +config KERNEL_INSTALL_V_2_6_24_2
16.127 + bool
16.128 + prompt "2.6.24.2"
16.129 + depends on KERNEL_VERSION_SEE_EXTRAVERSION
16.130 +
16.131 +# CT_INSERT_VERSION_ABOVE
16.132 +# Don't remove above line!
16.133 +endchoice
16.134 +
16.135 +config KERNEL_VERSION
16.136 + string
16.137 + default "2.6.18.8" if KERNEL_INSTALL_V_2_6_18_8
16.138 + default "2.6.19.7" if KERNEL_INSTALL_V_2_6_19_7
16.139 + default "2.6.20.21" if KERNEL_INSTALL_V_2_6_20_21
16.140 + default "2.6.21.7" if KERNEL_INSTALL_V_2_6_21_7
16.141 + default "2.6.22.18" if KERNEL_INSTALL_V_2_6_22_18
16.142 + default "2.6.23" if KERNEL_INSTALL_V_2_6_23
16.143 + default "2.6.23.1" if KERNEL_INSTALL_V_2_6_23_1
16.144 + default "2.6.23.2" if KERNEL_INSTALL_V_2_6_23_2
16.145 + default "2.6.23.3" if KERNEL_INSTALL_V_2_6_23_3
16.146 + default "2.6.23.4" if KERNEL_INSTALL_V_2_6_23_4
16.147 + default "2.6.23.5" if KERNEL_INSTALL_V_2_6_23_5
16.148 + default "2.6.23.6" if KERNEL_INSTALL_V_2_6_23_6
16.149 + default "2.6.23.7" if KERNEL_INSTALL_V_2_6_23_7
16.150 + default "2.6.23.8" if KERNEL_INSTALL_V_2_6_23_8
16.151 + default "2.6.23.9" if KERNEL_INSTALL_V_2_6_23_9
16.152 + default "2.6.23.10" if KERNEL_INSTALL_V_2_6_23_10
16.153 + default "2.6.23.11" if KERNEL_INSTALL_V_2_6_23_11
16.154 + default "2.6.23.12" if KERNEL_INSTALL_V_2_6_23_12
16.155 + default "2.6.23.13" if KERNEL_INSTALL_V_2_6_23_13
16.156 + default "2.6.23.14" if KERNEL_INSTALL_V_2_6_23_14
16.157 + default "2.6.23.15" if KERNEL_INSTALL_V_2_6_23_15
16.158 + default "2.6.23.16" if KERNEL_INSTALL_V_2_6_23_16
16.159 + default "2.6.24" if KERNEL_INSTALL_V_2_6_24
16.160 + default "2.6.24.1" if KERNEL_INSTALL_V_2_6_24_1
16.161 + default "2.6.24.2" if KERNEL_INSTALL_V_2_6_24_2
16.162 +# CT_INSERT_VERSION_STRING_ABOVE
16.163 +# Don't remove above line!
16.164 +
16.165 +config KERNEL_LINUX_HEADERS_INSTALL_CHECK
16.166 + bool
16.167 + prompt "Check installed headers"
16.168 + default n
16.169 + help
16.170 + If you are in doubt that installed headers are buggy, say 'Y'
16.171 + here to have an extra check passed onto the headers.
17.1 --- /dev/null Thu Jan 01 00:00:00 1970 +0000
17.2 +++ b/config/kernel/kernel_linux_headers_sanitised.in Thu Apr 17 20:26:25 2008 +0000
17.3 @@ -0,0 +1,62 @@
17.4 +choice
17.5 + bool
17.6 + prompt "Linux headers version"
17.7 +
17.8 +config KERNEL_SANITISED_V_2_6_7_0
17.9 + bool
17.10 + prompt "2.6.7.0"
17.11 +
17.12 +config KERNEL_SANITISED_V_2_6_8_0
17.13 + bool
17.14 + prompt "2.6.8.0"
17.15 +
17.16 +config KERNEL_SANITISED_V_2_6_8_1
17.17 + bool
17.18 + prompt "2.6.8.1"
17.19 +
17.20 +config KERNEL_SANITISED_V_2_6_9_0
17.21 + bool
17.22 + prompt "2.6.9.0"
17.23 +
17.24 +config KERNEL_SANITISED_V_2_6_9_1
17.25 + bool
17.26 + prompt "2.6.9.1"
17.27 +
17.28 +config KERNEL_SANITISED_V_2_6_10_0
17.29 + bool
17.30 + prompt "2.6.10.0"
17.31 +
17.32 +config KERNEL_SANITISED_V_2_6_11_0
17.33 + bool
17.34 + prompt "2.6.11.0"
17.35 +
17.36 +config KERNEL_SANITISED_V_2_6_11_1
17.37 + bool
17.38 + prompt "2.6.11.1"
17.39 +
17.40 +config KERNEL_SANITISED_V_2_6_11_2
17.41 + bool
17.42 + prompt "2.6.11.2"
17.43 +
17.44 +config KERNEL_SANITISED_V_2_6_12_0
17.45 + bool
17.46 + prompt "2.6.12.0"
17.47 +
17.48 +# CT_INSERT_VERSION_ABOVE
17.49 +# Don't remove above line!
17.50 +endchoice
17.51 +
17.52 +config KERNEL_VERSION
17.53 + string
17.54 + default "2.6.7.0" if KERNEL_SANITISED_V_2_6_7_0
17.55 + default "2.6.8.0" if KERNEL_SANITISED_V_2_6_8_0
17.56 + default "2.6.8.1" if KERNEL_SANITISED_V_2_6_8_1
17.57 + default "2.6.9.0" if KERNEL_SANITISED_V_2_6_9_0
17.58 + default "2.6.9.1" if KERNEL_SANITISED_V_2_6_9_1
17.59 + default "2.6.10.0" if KERNEL_SANITISED_V_2_6_10_0
17.60 + default "2.6.11.0" if KERNEL_SANITISED_V_2_6_11_0
17.61 + default "2.6.11.1" if KERNEL_SANITISED_V_2_6_11_1
17.62 + default "2.6.11.2" if KERNEL_SANITISED_V_2_6_11_2
17.63 + default "2.6.12.0" if KERNEL_SANITISED_V_2_6_12_0
17.64 +# CT_INSERT_VERSION_STRING_ABOVE
17.65 +# Don't remove above line!
18.1 --- a/config/kernel_linux.in Thu Apr 17 20:02:07 2008 +0000
18.2 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000
18.3 @@ -1,134 +0,0 @@
18.4 -# Linux kernel options
18.5 -
18.6 -choice
18.7 - bool
18.8 - prompt "Get kernel headers from:"
18.9 -
18.10 -config KERNEL_LINUX_HEADERS_INSTALL
18.11 - bool
18.12 - prompt "kernel's 'headers_install'"
18.13 - help
18.14 - This will make use of the new headers_install rule in recent kernels.
18.15 - This is most probably what you want to use.
18.16 -
18.17 -config KERNEL_LINUX_HEADERS_SANITISED
18.18 - bool
18.19 - prompt "Mazur's sanitized headers (OBSOLETE)"
18.20 - depends on OBSOLETE
18.21 - select KERNEL_LINUX_NEEDS_CONFIG
18.22 - help
18.23 - M. Mazur used to maintain a tree of sanitised headers, but it is now
18.24 - obsoleted by the headers_install rule (above), and has not seen any
18.25 - update since 2.6.12
18.26 -
18.27 -config KERNEL_LINUX_HEADERS_COPY
18.28 - bool
18.29 - prompt "pure kernel headers (REALLY OBSOLETE)"
18.30 - depends on OBSOLETE
18.31 - select KERNEL_LINUX_NEEDS_CONFIG
18.32 - help
18.33 - This will simply copy the kernel headers to the toolchain.
18.34 -
18.35 - You do NOT want this. It's badly broken because it leaks kernel internals
18.36 - to userspace.
18.37 -
18.38 -config KERNEL_LINUX_HEADERS_USE_CUSTOM_DIR
18.39 - bool
18.40 - prompt "Use custom directory"
18.41 - help
18.42 - If you have some kernel headers lying around, you can enter the path
18.43 - below.
18.44 -
18.45 -endchoice
18.46 -
18.47 -config KERNEL
18.48 - string
18.49 - default "linux" if ! KERNEL_LINUX_HEADERS_SANITISED
18.50 - default "linux-libc-headers" if KERNEL_LINUX_HEADERS_SANITISED
18.51 -
18.52 -config KERNEL_VERSION_SEE_EXTRAVERSION
18.53 - bool
18.54 - prompt "See extra versions"
18.55 - default n
18.56 - depends on KERNEL_LINUX_HEADERS_COPY || KERNEL_LINUX_HEADERS_INSTALL
18.57 - help
18.58 - See extra versions (kernel with 4 numbers, eg 2.6.19.1).
18.59 -
18.60 - If you say 'no', you'll only see sub-level, 3-digit versions.
18.61 - If you say 'yes', you'll see far more versions!
18.62 -
18.63 - It is recommended that you say 'no', unless you _*know*_
18.64 - that an extra version fixes a headers bug.
18.65 -
18.66 -if KERNEL_LINUX_HEADERS_INSTALL
18.67 -source config/kernel_linux_headers_install.in
18.68 -endif
18.69 -
18.70 -if KERNEL_LINUX_HEADERS_COPY
18.71 -source config/kernel_linux_headers_copy.in
18.72 -endif
18.73 -
18.74 -if KERNEL_LINUX_HEADERS_SANITISED
18.75 -source config/kernel_linux_headers_sanitised.in
18.76 -endif
18.77 -
18.78 -config KERNEL_LINUX_HEADERS_CUSTOM_DIR
18.79 - string
18.80 - prompt "Where are those custom headers?"
18.81 - depends on KERNEL_LINUX_HEADERS_USE_CUSTOM_DIR
18.82 - help
18.83 - Enter the base directory where the headers are to be found.
18.84 -
18.85 - Eg. if the headers are in /some/place/include, then enter /some/place.
18.86 - This is the same path you entered when you typed:
18.87 - make INSTALL_HDR_PATH=/some/place headers_install
18.88 -
18.89 -if ! KERNEL_LINUX_HEADERS_USE_CUSTOM_DIR
18.90 -
18.91 -choice
18.92 - bool
18.93 - prompt "Kernel verbosity:"
18.94 - default KERNEL_LINUX_VERBOSITY_0
18.95 -
18.96 -config KERNEL_LINUX_VERBOSITY_0
18.97 - bool
18.98 - prompt "Simplified"
18.99 - help
18.100 - Print simplified command lines.
18.101 -
18.102 -config KERNEL_LINUX_VERBOSITY_1
18.103 - bool
18.104 - prompt "Full commands"
18.105 - help
18.106 - Print full command lines.
18.107 -
18.108 -config KERNEL_LINUX_VERBOSITY_2
18.109 - bool
18.110 - prompt "Exec reasons"
18.111 - help
18.112 - Print the reasons why a make target is rebuild.
18.113 -
18.114 -endchoice
18.115 -
18.116 -config KERNEL_LINUX_VERBOSE_LEVEL
18.117 - int
18.118 - default 0 if KERNEL_LINUX_VERBOSITY_0
18.119 - default 1 if KERNEL_LINUX_VERBOSITY_1
18.120 - default 2 if KERNEL_LINUX_VERBOSITY_2
18.121 -
18.122 -config KERNEL_LINUX_NEEDS_CONFIG
18.123 - bool
18.124 - default n
18.125 -
18.126 -config KERNEL_LINUX_CONFIG_FILE
18.127 - string
18.128 - prompt "Configuration file"
18.129 - depends on KERNEL_LINUX_NEEDS_CONFIG
18.130 - default ""
18.131 - help
18.132 - Path to a kernel configuration file.
18.133 -
18.134 - If you don't provide one, then the default configuration for
18.135 - your target will be used.
18.136 -
18.137 -endif
19.1 --- a/config/kernel_linux_headers_copy.in Thu Apr 17 20:02:07 2008 +0000
19.2 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000
19.3 @@ -1,42 +0,0 @@
19.4 -choice
19.5 - bool
19.6 - prompt "Linux kernel version"
19.7 -
19.8 -config KERNEL_COPY_V_2_4_26
19.9 - bool
19.10 - prompt "2.4.26"
19.11 -
19.12 -config KERNEL_COPY_V_2_6_5
19.13 - bool
19.14 - prompt "2.6.5"
19.15 -
19.16 -config KERNEL_COPY_V_2_6_6
19.17 - bool
19.18 - prompt "2.6.6"
19.19 -
19.20 -config KERNEL_COPY_V_2_6_7
19.21 - bool
19.22 - prompt "2.6.7"
19.23 -
19.24 -config KERNEL_COPY_V_2_6_8
19.25 - bool
19.26 - prompt "2.6.8"
19.27 -
19.28 -config KERNEL_COPY_V_2_6_11_3
19.29 - bool
19.30 - prompt "2.6.11.3"
19.31 - depends on KERNEL_VERSION_SEE_EXTRAVERSION
19.32 -
19.33 -# CT_INSERT_VERSION_ABOVE
19.34 -# Don't remove above line!
19.35 -endchoice
19.36 -
19.37 -config KERNEL_VERSION
19.38 - string
19.39 - default "2.6.5" if KERNEL_COPY_V_2_6_5
19.40 - default "2.6.6" if KERNEL_COPY_V_2_6_6
19.41 - default "2.6.7" if KERNEL_COPY_V_2_6_7
19.42 - default "2.6.8" if KERNEL_COPY_V_2_6_8
19.43 - default "2.6.11.3" if KERNEL_COPY_V_2_6_11_3
19.44 -# CT_INSERT_VERSION_STRING_ABOVE
19.45 -# Don't remove above line!
20.1 --- a/config/kernel_linux_headers_install.in Thu Apr 17 20:02:07 2008 +0000
20.2 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000
20.3 @@ -1,168 +0,0 @@
20.4 -choice
20.5 - bool
20.6 - prompt "Linux kernel version"
20.7 -
20.8 -config KERNEL_INSTALL_V_2_6_18_8
20.9 - bool
20.10 - prompt "2.6.18.8 (OBSOLETE)"
20.11 - depends on KERNEL_VERSION_SEE_EXTRAVERSION && OBSOLETE
20.12 -
20.13 -config KERNEL_INSTALL_V_2_6_19_7
20.14 - bool
20.15 - prompt "2.6.19.7 (OBSOLETE)"
20.16 - depends on KERNEL_VERSION_SEE_EXTRAVERSION && OBSOLETE
20.17 -
20.18 -config KERNEL_INSTALL_V_2_6_20_21
20.19 - bool
20.20 - prompt "2.6.20.21 (OBSOLETE)"
20.21 - depends on KERNEL_VERSION_SEE_EXTRAVERSION && OBSOLETE
20.22 -
20.23 -config KERNEL_INSTALL_V_2_6_21_7
20.24 - bool
20.25 - prompt "2.6.21.7 (OBSOLETE)"
20.26 - depends on KERNEL_VERSION_SEE_EXTRAVERSION && OBSOLETE
20.27 -
20.28 -config KERNEL_INSTALL_V_2_6_22_18
20.29 - bool
20.30 - prompt "2.6.22.18"
20.31 - depends on KERNEL_VERSION_SEE_EXTRAVERSION
20.32 -
20.33 -config KERNEL_INSTALL_V_2_6_23
20.34 - bool
20.35 - prompt "2.6.23"
20.36 -
20.37 -config KERNEL_INSTALL_V_2_6_23_1
20.38 - bool
20.39 - prompt "2.6.23.1"
20.40 - depends on KERNEL_VERSION_SEE_EXTRAVERSION
20.41 -
20.42 -config KERNEL_INSTALL_V_2_6_23_2
20.43 - bool
20.44 - prompt "2.6.23.2"
20.45 - depends on KERNEL_VERSION_SEE_EXTRAVERSION
20.46 -
20.47 -config KERNEL_INSTALL_V_2_6_23_3
20.48 - bool
20.49 - prompt "2.6.23.3"
20.50 - depends on KERNEL_VERSION_SEE_EXTRAVERSION
20.51 -
20.52 -config KERNEL_INSTALL_V_2_6_23_4
20.53 - bool
20.54 - prompt "2.6.23.4"
20.55 - depends on KERNEL_VERSION_SEE_EXTRAVERSION
20.56 -
20.57 -config KERNEL_INSTALL_V_2_6_23_5
20.58 - bool
20.59 - prompt "2.6.23.5"
20.60 - depends on KERNEL_VERSION_SEE_EXTRAVERSION
20.61 -
20.62 -config KERNEL_INSTALL_V_2_6_23_6
20.63 - bool
20.64 - prompt "2.6.23.6"
20.65 - depends on KERNEL_VERSION_SEE_EXTRAVERSION
20.66 -
20.67 -config KERNEL_INSTALL_V_2_6_23_7
20.68 - bool
20.69 - prompt "2.6.23.7"
20.70 - depends on KERNEL_VERSION_SEE_EXTRAVERSION
20.71 -
20.72 -config KERNEL_INSTALL_V_2_6_23_8
20.73 - bool
20.74 - prompt "2.6.23.8"
20.75 - depends on KERNEL_VERSION_SEE_EXTRAVERSION
20.76 -
20.77 -config KERNEL_INSTALL_V_2_6_23_9
20.78 - bool
20.79 - prompt "2.6.23.9"
20.80 - depends on KERNEL_VERSION_SEE_EXTRAVERSION
20.81 -
20.82 -config KERNEL_INSTALL_V_2_6_23_10
20.83 - bool
20.84 - prompt "2.6.23.10"
20.85 - depends on KERNEL_VERSION_SEE_EXTRAVERSION
20.86 -
20.87 -config KERNEL_INSTALL_V_2_6_23_11
20.88 - bool
20.89 - prompt "2.6.23.11"
20.90 - depends on KERNEL_VERSION_SEE_EXTRAVERSION
20.91 -
20.92 -config KERNEL_INSTALL_V_2_6_23_12
20.93 - bool
20.94 - prompt "2.6.23.12"
20.95 - depends on KERNEL_VERSION_SEE_EXTRAVERSION
20.96 -
20.97 -config KERNEL_INSTALL_V_2_6_23_13
20.98 - bool
20.99 - prompt "2.6.23.13"
20.100 - depends on KERNEL_VERSION_SEE_EXTRAVERSION
20.101 -
20.102 -config KERNEL_INSTALL_V_2_6_23_14
20.103 - bool
20.104 - prompt "2.6.23.14"
20.105 - depends on KERNEL_VERSION_SEE_EXTRAVERSION
20.106 -
20.107 -config KERNEL_INSTALL_V_2_6_23_15
20.108 - bool
20.109 - prompt "2.6.23.15"
20.110 - depends on KERNEL_VERSION_SEE_EXTRAVERSION
20.111 -
20.112 -config KERNEL_INSTALL_V_2_6_23_16
20.113 - bool
20.114 - prompt "2.6.23.16"
20.115 - depends on KERNEL_VERSION_SEE_EXTRAVERSION
20.116 -
20.117 -config KERNEL_INSTALL_V_2_6_24
20.118 - bool
20.119 - prompt "2.6.24"
20.120 -
20.121 -config KERNEL_INSTALL_V_2_6_24_1
20.122 - bool
20.123 - prompt "2.6.24.1"
20.124 - depends on KERNEL_VERSION_SEE_EXTRAVERSION
20.125 -
20.126 -config KERNEL_INSTALL_V_2_6_24_2
20.127 - bool
20.128 - prompt "2.6.24.2"
20.129 - depends on KERNEL_VERSION_SEE_EXTRAVERSION
20.130 -
20.131 -# CT_INSERT_VERSION_ABOVE
20.132 -# Don't remove above line!
20.133 -endchoice
20.134 -
20.135 -config KERNEL_VERSION
20.136 - string
20.137 - default "2.6.18.8" if KERNEL_INSTALL_V_2_6_18_8
20.138 - default "2.6.19.7" if KERNEL_INSTALL_V_2_6_19_7
20.139 - default "2.6.20.21" if KERNEL_INSTALL_V_2_6_20_21
20.140 - default "2.6.21.7" if KERNEL_INSTALL_V_2_6_21_7
20.141 - default "2.6.22.18" if KERNEL_INSTALL_V_2_6_22_18
20.142 - default "2.6.23" if KERNEL_INSTALL_V_2_6_23
20.143 - default "2.6.23.1" if KERNEL_INSTALL_V_2_6_23_1
20.144 - default "2.6.23.2" if KERNEL_INSTALL_V_2_6_23_2
20.145 - default "2.6.23.3" if KERNEL_INSTALL_V_2_6_23_3
20.146 - default "2.6.23.4" if KERNEL_INSTALL_V_2_6_23_4
20.147 - default "2.6.23.5" if KERNEL_INSTALL_V_2_6_23_5
20.148 - default "2.6.23.6" if KERNEL_INSTALL_V_2_6_23_6
20.149 - default "2.6.23.7" if KERNEL_INSTALL_V_2_6_23_7
20.150 - default "2.6.23.8" if KERNEL_INSTALL_V_2_6_23_8
20.151 - default "2.6.23.9" if KERNEL_INSTALL_V_2_6_23_9
20.152 - default "2.6.23.10" if KERNEL_INSTALL_V_2_6_23_10
20.153 - default "2.6.23.11" if KERNEL_INSTALL_V_2_6_23_11
20.154 - default "2.6.23.12" if KERNEL_INSTALL_V_2_6_23_12
20.155 - default "2.6.23.13" if KERNEL_INSTALL_V_2_6_23_13
20.156 - default "2.6.23.14" if KERNEL_INSTALL_V_2_6_23_14
20.157 - default "2.6.23.15" if KERNEL_INSTALL_V_2_6_23_15
20.158 - default "2.6.23.16" if KERNEL_INSTALL_V_2_6_23_16
20.159 - default "2.6.24" if KERNEL_INSTALL_V_2_6_24
20.160 - default "2.6.24.1" if KERNEL_INSTALL_V_2_6_24_1
20.161 - default "2.6.24.2" if KERNEL_INSTALL_V_2_6_24_2
20.162 -# CT_INSERT_VERSION_STRING_ABOVE
20.163 -# Don't remove above line!
20.164 -
20.165 -config KERNEL_LINUX_HEADERS_INSTALL_CHECK
20.166 - bool
20.167 - prompt "Check installed headers"
20.168 - default n
20.169 - help
20.170 - If you are in doubt that installed headers are buggy, say 'Y'
20.171 - here to have an extra check passed onto the headers.
21.1 --- a/config/kernel_linux_headers_sanitised.in Thu Apr 17 20:02:07 2008 +0000
21.2 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000
21.3 @@ -1,62 +0,0 @@
21.4 -choice
21.5 - bool
21.6 - prompt "Linux headers version"
21.7 -
21.8 -config KERNEL_SANITISED_V_2_6_7_0
21.9 - bool
21.10 - prompt "2.6.7.0"
21.11 -
21.12 -config KERNEL_SANITISED_V_2_6_8_0
21.13 - bool
21.14 - prompt "2.6.8.0"
21.15 -
21.16 -config KERNEL_SANITISED_V_2_6_8_1
21.17 - bool
21.18 - prompt "2.6.8.1"
21.19 -
21.20 -config KERNEL_SANITISED_V_2_6_9_0
21.21 - bool
21.22 - prompt "2.6.9.0"
21.23 -
21.24 -config KERNEL_SANITISED_V_2_6_9_1
21.25 - bool
21.26 - prompt "2.6.9.1"
21.27 -
21.28 -config KERNEL_SANITISED_V_2_6_10_0
21.29 - bool
21.30 - prompt "2.6.10.0"
21.31 -
21.32 -config KERNEL_SANITISED_V_2_6_11_0
21.33 - bool
21.34 - prompt "2.6.11.0"
21.35 -
21.36 -config KERNEL_SANITISED_V_2_6_11_1
21.37 - bool
21.38 - prompt "2.6.11.1"
21.39 -
21.40 -config KERNEL_SANITISED_V_2_6_11_2
21.41 - bool
21.42 - prompt "2.6.11.2"
21.43 -
21.44 -config KERNEL_SANITISED_V_2_6_12_0
21.45 - bool
21.46 - prompt "2.6.12.0"
21.47 -
21.48 -# CT_INSERT_VERSION_ABOVE
21.49 -# Don't remove above line!
21.50 -endchoice
21.51 -
21.52 -config KERNEL_VERSION
21.53 - string
21.54 - default "2.6.7.0" if KERNEL_SANITISED_V_2_6_7_0
21.55 - default "2.6.8.0" if KERNEL_SANITISED_V_2_6_8_0
21.56 - default "2.6.8.1" if KERNEL_SANITISED_V_2_6_8_1
21.57 - default "2.6.9.0" if KERNEL_SANITISED_V_2_6_9_0
21.58 - default "2.6.9.1" if KERNEL_SANITISED_V_2_6_9_1
21.59 - default "2.6.10.0" if KERNEL_SANITISED_V_2_6_10_0
21.60 - default "2.6.11.0" if KERNEL_SANITISED_V_2_6_11_0
21.61 - default "2.6.11.1" if KERNEL_SANITISED_V_2_6_11_1
21.62 - default "2.6.11.2" if KERNEL_SANITISED_V_2_6_11_2
21.63 - default "2.6.12.0" if KERNEL_SANITISED_V_2_6_12_0
21.64 -# CT_INSERT_VERSION_STRING_ABOVE
21.65 -# Don't remove above line!
22.1 --- a/config/libc.in Thu Apr 17 20:02:07 2008 +0000
22.2 +++ b/config/libc.in Thu Apr 17 20:26:25 2008 +0000
22.3 @@ -37,11 +37,11 @@
22.4 default n
22.5
22.6 if LIBC_GLIBC
22.7 -source config/libc_glibc.in
22.8 +source config/libc/libc_glibc.in
22.9 endif
22.10
22.11 if LIBC_UCLIBC
22.12 -source config/libc_uClibc.in
22.13 +source config/libc/libc_uClibc.in
22.14 endif
22.15
22.16 endmenu
23.1 --- /dev/null Thu Jan 01 00:00:00 1970 +0000
23.2 +++ b/config/libc/libc_glibc.in Thu Apr 17 20:26:25 2008 +0000
23.3 @@ -0,0 +1,124 @@
23.4 +# glibc options
23.5 +
23.6 +choice
23.7 + bool
23.8 + prompt "glibc version"
23.9 +
23.10 +config LIBC_V_2_3_6
23.11 + bool
23.12 + prompt "2.3.6 (OBSOLETE)"
23.13 + depends on OBSOLETE
23.14 +
23.15 +config LIBC_V_2_5
23.16 + bool
23.17 + prompt "2.5"
23.18 +
23.19 +config LIBC_V_2_5_1
23.20 + bool
23.21 + prompt "2.5.1"
23.22 +
23.23 +config LIBC_V_2_6
23.24 + bool
23.25 + prompt "2.6"
23.26 +
23.27 +config LIBC_V_2_6_1
23.28 + bool
23.29 + prompt "2.6.1"
23.30 +
23.31 +config LIBC_V_2_7
23.32 + bool
23.33 + prompt "2.7"
23.34 + depends on EXPERIMENTAL
23.35 +
23.36 +# CT_INSERT_VERSION_ABOVE
23.37 +# Don't remove above line!
23.38 +endchoice
23.39 +
23.40 +config LIBC_VERSION
23.41 + string
23.42 + default "2.3.6" if LIBC_V_2_3_6
23.43 + default "2.4" if LIBC_V_2_4
23.44 + default "2.5" if LIBC_V_2_5
23.45 + default "2.5.1" if LIBC_V_2_5_1
23.46 + default "2.6" if LIBC_V_2_6
23.47 + default "2.6.1" if LIBC_V_2_6_1
23.48 + default "2.7" if LIBC_V_2_7
23.49 +# CT_INSERT_VERSION_STRING_ABOVE
23.50 +# Don't remove above line!
23.51 +
23.52 +config LIBC_GLIBC_EXTRA_CONFIG
23.53 + string
23.54 + prompt "glibc extra config"
23.55 + default ""
23.56 + help
23.57 + Extra flags to pass onto ./configure when configuring glibc.
23.58 +
23.59 + Eg.: --enable-static-nss
23.60 +
23.61 +config LIBC_GLIBC_EXTRA_CFLAGS
23.62 + string
23.63 + prompt "glibc extra target CFLAGS"
23.64 + default ""
23.65 + help
23.66 + Extra target CFLAGS to use when building glibc.
23.67 +
23.68 +config LIBC_EXTRA_CC_ARGS
23.69 + string
23.70 + prompt "gcc extra flags"
23.71 + default ""
23.72 + help
23.73 + Extra flags to pass gcc when building glibc.
23.74 +
23.75 + Seldom used, except for sparc64 which seems to need the flag -64
23.76 + to be passed onto gcc.
23.77 +
23.78 +# Please note: This is not used for now (no sh support).
23.79 +config LIBC_GLIBC_CONFIGPARMS
23.80 + string
23.81 + prompt "Extra config params (READ HELP)"
23.82 + default "" if ARCH != "sh3" && ARCH != "sh4"
23.83 + default "no-z-defs=yes" if ARCH = "sh3" || ARCH = "sh4"
23.84 + help
23.85 + Some architectures need to set options in the file configparms.
23.86 + This is the case for sh3/4, which really need to set configparms as of
23.87 + gcc-3.4/glibc-2.3.2.
23.88 +
23.89 + Unless you are building a toolchain for sh3/4, you should leave that empty.
23.90 +
23.91 + Note: this is awkward, doesn't work well if you need more than one
23.92 + line in configparms
23.93 +
23.94 +config LIBC_GLIBC_USE_PORTS
23.95 + bool
23.96 + prompt "Use the ports addon"
23.97 + default n
23.98 + help
23.99 + The ports addon contains some architecture ports that are not available
23.100 + in the official glibc distribution.
23.101 +
23.102 + For example, this is the case for ARM with glibc >= 2.4
23.103 +
23.104 + Say n only if you're sure that your architecture is in the official
23.105 + glibc distribution for your chosen version.
23.106 +
23.107 +config LIBC_ADDONS
23.108 + bool
23.109 + prompt "Pass extra addons list"
23.110 + default n
23.111 + help
23.112 + If you say Y here, you'll be able to give the list of addons you want to
23.113 + include in your C library.
23.114 +
23.115 +config LIBC_ADDONS_LIST
23.116 + string
23.117 + prompt "Extra addons"
23.118 + default ""
23.119 + depends on LIBC_ADDONS
23.120 + help
23.121 + Extra addons to include in glibc. Space separated list.
23.122 +
23.123 + You need to specify neither linuxthreads nor nptl, as they are added
23.124 + automagically for you depending on the threading model you choosed
23.125 + earlier.
23.126 +
23.127 + Eg.: crypt (for very old glibces)
24.1 --- /dev/null Thu Jan 01 00:00:00 1970 +0000
24.2 +++ b/config/libc/libc_uClibc.in Thu Apr 17 20:26:25 2008 +0000
24.3 @@ -0,0 +1,101 @@
24.4 +# uClibc options
24.5 +
24.6 +choice
24.7 + bool
24.8 + prompt "uClibc version"
24.9 +
24.10 +config LIBC_V_snapshot
24.11 + bool
24.12 + prompt "latest snapshot"
24.13 +
24.14 +config LIBC_V_specific_date
24.15 + bool
24.16 + prompt "<specific date>"
24.17 +
24.18 +config LIBC_V_0_9_28
24.19 + bool
24.20 + prompt "0.9.28 (OBSOLETE)"
24.21 + depends on OBSOLETE
24.22 +
24.23 +config LIBC_V_0_9_28_1
24.24 + bool
24.25 + prompt "0.9.28.1 (OBSOLETE)"
24.26 + depends on OBSOLETE
24.27 +
24.28 +config LIBC_V_0_9_28_2
24.29 + bool
24.30 + prompt "0.9.28.2 (OBSOLETE)"
24.31 + depends on OBSOLETE
24.32 +
24.33 +config LIBC_V_0_9_28_3
24.34 + bool
24.35 + prompt "0.9.28.3"
24.36 +
24.37 +config LIBC_V_0_9_29
24.38 + bool
24.39 + prompt "0.9.29"
24.40 +
24.41 +# CT_INSERT_VERSION_ABOVE
24.42 +# Don't remove above line!
24.43 +endchoice
24.44 +
24.45 +config LIBC_VERSION
24.46 + string
24.47 + prompt "Enter date (YYYYMMDD)" if LIBC_V_specific_date
24.48 + default "snapshot" if LIBC_V_snapshot
24.49 + default "0.9.28" if LIBC_V_0_9_28
24.50 + default "0.9.28.1" if LIBC_V_0_9_28_1
24.51 + default "0.9.28.2" if LIBC_V_0_9_28_2
24.52 + default "0.9.28.3" if LIBC_V_0_9_28_3
24.53 + default "0.9.29" if LIBC_V_0_9_29
24.54 +# CT_INSERT_VERSION_STRING_ABOVE
24.55 +# Don't remove above line!
24.56 + help
24.57 + Enter the date of the snapshot you want to use in the form: YYYYMMDD
24.58 + where YYYY is the 4-digit year, MM the 2-digit month and DD the 2-digit
24.59 + day in the month.
24.60 +
24.61 + Please note that uClibc site removes snapshots older than a month.
24.62 +
24.63 +choice
24.64 + bool
24.65 + prompt "Debug level"
24.66 + default LIBC_UCLIBC_DEBUG_LEVEL_0
24.67 +
24.68 +config LIBC_UCLIBC_DEBUG_LEVEL_0
24.69 + bool
24.70 + prompt "none"
24.71 +
24.72 +config LIBC_UCLIBC_DEBUG_LEVEL_1
24.73 + bool
24.74 + prompt "minimal"
24.75 +
24.76 +config LIBC_UCLIBC_DEBUG_LEVEL_2
24.77 + bool
24.78 + prompt "all"
24.79 +
24.80 +endchoice
24.81 +
24.82 +config LIBC_UCLIBC_DEBUG_LEVEL
24.83 + int
24.84 + default 0 if LIBC_UCLIBC_DEBUG_LEVEL_0
24.85 + default 1 if LIBC_UCLIBC_DEBUG_LEVEL_1
24.86 + default 2 if LIBC_UCLIBC_DEBUG_LEVEL_2
24.87 +
24.88 +config LIBC_UCLIBC_CONFIG_FILE
24.89 + string
24.90 + prompt "Configuration file"
24.91 + default ""
24.92 + help
24.93 + Path to the configuration file.
24.94 +
24.95 + You _must_ provide one (for now).
24.96 +
24.97 +config LIBC_UCLIBC_LOCALES
24.98 + bool
24.99 + prompt "Add support for locales"
24.100 + default n
24.101 + help
24.102 + Say y if you want uClibc to support localisation.
24.103 +
24.104 + Note that seems to be broken on recent uClibc releases.
25.1 --- a/config/libc_glibc.in Thu Apr 17 20:02:07 2008 +0000
25.2 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000
25.3 @@ -1,124 +0,0 @@
25.4 -# glibc options
25.5 -
25.6 -choice
25.7 - bool
25.8 - prompt "glibc version"
25.9 -
25.10 -config LIBC_V_2_3_6
25.11 - bool
25.12 - prompt "2.3.6 (OBSOLETE)"
25.13 - depends on OBSOLETE
25.14 -
25.15 -config LIBC_V_2_5
25.16 - bool
25.17 - prompt "2.5"
25.18 -
25.19 -config LIBC_V_2_5_1
25.20 - bool
25.21 - prompt "2.5.1"
25.22 -
25.23 -config LIBC_V_2_6
25.24 - bool
25.25 - prompt "2.6"
25.26 -
25.27 -config LIBC_V_2_6_1
25.28 - bool
25.29 - prompt "2.6.1"
25.30 -
25.31 -config LIBC_V_2_7
25.32 - bool
25.33 - prompt "2.7"
25.34 - depends on EXPERIMENTAL
25.35 -
25.36 -# CT_INSERT_VERSION_ABOVE
25.37 -# Don't remove above line!
25.38 -endchoice
25.39 -
25.40 -config LIBC_VERSION
25.41 - string
25.42 - default "2.3.6" if LIBC_V_2_3_6
25.43 - default "2.4" if LIBC_V_2_4
25.44 - default "2.5" if LIBC_V_2_5
25.45 - default "2.5.1" if LIBC_V_2_5_1
25.46 - default "2.6" if LIBC_V_2_6
25.47 - default "2.6.1" if LIBC_V_2_6_1
25.48 - default "2.7" if LIBC_V_2_7
25.49 -# CT_INSERT_VERSION_STRING_ABOVE
25.50 -# Don't remove above line!
25.51 -
25.52 -config LIBC_GLIBC_EXTRA_CONFIG
25.53 - string
25.54 - prompt "glibc extra config"
25.55 - default ""
25.56 - help
25.57 - Extra flags to pass onto ./configure when configuring glibc.
25.58 -
25.59 - Eg.: --enable-static-nss
25.60 -
25.61 -config LIBC_GLIBC_EXTRA_CFLAGS
25.62 - string
25.63 - prompt "glibc extra target CFLAGS"
25.64 - default ""
25.65 - help
25.66 - Extra target CFLAGS to use when building glibc.
25.67 -
25.68 -config LIBC_EXTRA_CC_ARGS
25.69 - string
25.70 - prompt "gcc extra flags"
25.71 - default ""
25.72 - help
25.73 - Extra flags to pass gcc when building glibc.
25.74 -
25.75 - Seldom used, except for sparc64 which seems to need the flag -64
25.76 - to be passed onto gcc.
25.77 -
25.78 -# Please note: This is not used for now (no sh support).
25.79 -config LIBC_GLIBC_CONFIGPARMS
25.80 - string
25.81 - prompt "Extra config params (READ HELP)"
25.82 - default "" if ARCH != "sh3" && ARCH != "sh4"
25.83 - default "no-z-defs=yes" if ARCH = "sh3" || ARCH = "sh4"
25.84 - help
25.85 - Some architectures need to set options in the file configparms.
25.86 - This is the case for sh3/4, which really need to set configparms as of
25.87 - gcc-3.4/glibc-2.3.2.
25.88 -
25.89 - Unless you are building a toolchain for sh3/4, you should leave that empty.
25.90 -
25.91 - Note: this is awkward, doesn't work well if you need more than one
25.92 - line in configparms
25.93 -
25.94 -config LIBC_GLIBC_USE_PORTS
25.95 - bool
25.96 - prompt "Use the ports addon"
25.97 - default n
25.98 - help
25.99 - The ports addon contains some architecture ports that are not available
25.100 - in the official glibc distribution.
25.101 -
25.102 - For example, this is the case for ARM with glibc >= 2.4
25.103 -
25.104 - Say n only if you're sure that your architecture is in the official
25.105 - glibc distribution for your chosen version.
25.106 -
25.107 -config LIBC_ADDONS
25.108 - bool
25.109 - prompt "Pass extra addons list"
25.110 - default n
25.111 - help
25.112 - If you say Y here, you'll be able to give the list of addons you want to
25.113 - include in your C library.
25.114 -
25.115 -config LIBC_ADDONS_LIST
25.116 - string
25.117 - prompt "Extra addons"
25.118 - default ""
25.119 - depends on LIBC_ADDONS
25.120 - help
25.121 - Extra addons to include in glibc. Space separated list.
25.122 -
25.123 - You need to specify neither linuxthreads nor nptl, as they are added
25.124 - automagically for you depending on the threading model you choosed
25.125 - earlier.
25.126 -
25.127 - Eg.: crypt (for very old glibces)
26.1 --- a/config/libc_uClibc.in Thu Apr 17 20:02:07 2008 +0000
26.2 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000
26.3 @@ -1,101 +0,0 @@
26.4 -# uClibc options
26.5 -
26.6 -choice
26.7 - bool
26.8 - prompt "uClibc version"
26.9 -
26.10 -config LIBC_V_snapshot
26.11 - bool
26.12 - prompt "latest snapshot"
26.13 -
26.14 -config LIBC_V_specific_date
26.15 - bool
26.16 - prompt "<specific date>"
26.17 -
26.18 -config LIBC_V_0_9_28
26.19 - bool
26.20 - prompt "0.9.28 (OBSOLETE)"
26.21 - depends on OBSOLETE
26.22 -
26.23 -config LIBC_V_0_9_28_1
26.24 - bool
26.25 - prompt "0.9.28.1 (OBSOLETE)"
26.26 - depends on OBSOLETE
26.27 -
26.28 -config LIBC_V_0_9_28_2
26.29 - bool
26.30 - prompt "0.9.28.2 (OBSOLETE)"
26.31 - depends on OBSOLETE
26.32 -
26.33 -config LIBC_V_0_9_28_3
26.34 - bool
26.35 - prompt "0.9.28.3"
26.36 -
26.37 -config LIBC_V_0_9_29
26.38 - bool
26.39 - prompt "0.9.29"
26.40 -
26.41 -# CT_INSERT_VERSION_ABOVE
26.42 -# Don't remove above line!
26.43 -endchoice
26.44 -
26.45 -config LIBC_VERSION
26.46 - string
26.47 - prompt "Enter date (YYYYMMDD)" if LIBC_V_specific_date
26.48 - default "snapshot" if LIBC_V_snapshot
26.49 - default "0.9.28" if LIBC_V_0_9_28
26.50 - default "0.9.28.1" if LIBC_V_0_9_28_1
26.51 - default "0.9.28.2" if LIBC_V_0_9_28_2
26.52 - default "0.9.28.3" if LIBC_V_0_9_28_3
26.53 - default "0.9.29" if LIBC_V_0_9_29
26.54 -# CT_INSERT_VERSION_STRING_ABOVE
26.55 -# Don't remove above line!
26.56 - help
26.57 - Enter the date of the snapshot you want to use in the form: YYYYMMDD
26.58 - where YYYY is the 4-digit year, MM the 2-digit month and DD the 2-digit
26.59 - day in the month.
26.60 -
26.61 - Please note that uClibc site removes snapshots older than a month.
26.62 -
26.63 -choice
26.64 - bool
26.65 - prompt "Debug level"
26.66 - default LIBC_UCLIBC_DEBUG_LEVEL_0
26.67 -
26.68 -config LIBC_UCLIBC_DEBUG_LEVEL_0
26.69 - bool
26.70 - prompt "none"
26.71 -
26.72 -config LIBC_UCLIBC_DEBUG_LEVEL_1
26.73 - bool
26.74 - prompt "minimal"
26.75 -
26.76 -config LIBC_UCLIBC_DEBUG_LEVEL_2
26.77 - bool
26.78 - prompt "all"
26.79 -
26.80 -endchoice
26.81 -
26.82 -config LIBC_UCLIBC_DEBUG_LEVEL
26.83 - int
26.84 - default 0 if LIBC_UCLIBC_DEBUG_LEVEL_0
26.85 - default 1 if LIBC_UCLIBC_DEBUG_LEVEL_1
26.86 - default 2 if LIBC_UCLIBC_DEBUG_LEVEL_2
26.87 -
26.88 -config LIBC_UCLIBC_CONFIG_FILE
26.89 - string
26.90 - prompt "Configuration file"
26.91 - default ""
26.92 - help
26.93 - Path to the configuration file.
26.94 -
26.95 - You _must_ provide one (for now).
26.96 -
26.97 -config LIBC_UCLIBC_LOCALES
26.98 - bool
26.99 - prompt "Add support for locales"
26.100 - default n
26.101 - help
26.102 - Say y if you want uClibc to support localisation.
26.103 -
26.104 - Note that seems to be broken on recent uClibc releases.
27.1 --- a/config/logging.in Thu Apr 17 20:02:07 2008 +0000
27.2 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000
27.3 @@ -1,110 +0,0 @@
27.4 -# Options specific to logging
27.5 -
27.6 -comment "Logging"
27.7 -
27.8 -choice
27.9 - bool
27.10 - prompt "Maximum log level to see:"
27.11 - default LOG_INFO if !DEBUG_CT
27.12 - default LOG_DEBUG if DEBUG_CT
27.13 -
27.14 -config LOG_ERROR
27.15 - bool
27.16 - prompt "ERROR"
27.17 - help
27.18 - The build will be silent.
27.19 - Only if there is an error will you see a message.
27.20 -
27.21 -config LOG_WARN
27.22 - bool
27.23 - prompt "WARN"
27.24 - help
27.25 - The same as above, plus warnings.
27.26 -
27.27 -config LOG_INFO
27.28 - bool
27.29 - prompt "INFO"
27.30 - help
27.31 - The same as above, plus informational messages (main steps).
27.32 -
27.33 -config LOG_EXTRA
27.34 - bool
27.35 - prompt "EXTRA"
27.36 - help
27.37 - The same as above, plus extra messages (sub-steps).
27.38 -
27.39 -config LOG_DEBUG
27.40 - bool
27.41 - prompt "DEBUG"
27.42 - help
27.43 - The same as above, plus lots of crosstool-NG debug information.
27.44 -
27.45 -config LOG_ALL
27.46 - bool
27.47 - prompt "ALL"
27.48 - help
27.49 - The same as above, plus all components build messages (very noisy!).
27.50 -
27.51 -endchoice
27.52 -
27.53 -config LOG_LEVEL_MAX
27.54 - string
27.55 - default "ERROR" if LOG_ERROR
27.56 - default "WARN" if LOG_WARN
27.57 - default "INFO" if LOG_INFO
27.58 - default "EXTRA" if LOG_EXTRA
27.59 - default "DEBUG" if LOG_DEBUG
27.60 - default "ALL" if LOG_ALL
27.61 -
27.62 -config LOG_SEE_TOOLS_WARN
27.63 - bool
27.64 - prompt "Warnings from the tools' builds"
27.65 - default n
27.66 - depends on ! LOG_ERROR
27.67 - help
27.68 - Treat warnings from the different tools as crosstool-NG warnings.
27.69 - If you say 'y' here, then those warnings will be prefixed with
27.70 - '[WARN ]' instead of the default '[ALL ]'.
27.71 -
27.72 - You can safely say 'n' here. Those warnings will anyway be
27.73 - recorded in the log file (provided you configured one).
27.74 -
27.75 - Tools error will always be logged as crosstool-NG errors.
27.76 -
27.77 -config LOG_PROGRESS_BAR
27.78 - bool
27.79 - prompt "Progress bar"
27.80 - default y
27.81 - depends on ! LOG_ALL
27.82 - help
27.83 - If you say 'y' here, you'll be able to see the elapsed time.
27.84 -
27.85 - As a bonus, you'll also get a rotating bar (/-\|) showing you
27.86 - that the build is not stalled (the bar rotates 1/4 every 10 lines
27.87 - of components build log).
27.88 -
27.89 - Note that the elapsed time can stall for a little while if a
27.90 - component has long commands, as the elapsed time is only updated
27.91 - each line.
27.92 -
27.93 -config LOG_TO_FILE
27.94 - bool
27.95 - prompt "Log to a file"
27.96 - default y
27.97 - help
27.98 - Save *full* logs to a file. Even log levels you didn't specify above
27.99 - will be available in this file. The log file will be named build.log
27.100 - and stored in the toolchain prefix dir (set above).
27.101 -
27.102 - As a bonus, there is a script in tools/extractConfig.sh that is able
27.103 - to extract the configuration of crosstool-NG from the log file.
27.104 -
27.105 - Definitely, say Y.
27.106 -
27.107 -config LOG_FILE_COMPRESS
27.108 - bool
27.109 - prompt "Compress the log file"
27.110 - default n
27.111 - depends on LOG_TO_FILE
27.112 - help
27.113 - Compress the log file once the toolchain is successfully built.
28.1 --- a/config/paths.in Thu Apr 17 20:02:07 2008 +0000
28.2 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000
28.3 @@ -1,89 +0,0 @@
28.4 -# Options related to paths and install
28.5 -
28.6 -comment "Paths"
28.7 -
28.8 -config LOCAL_TARBALLS_DIR
28.9 - string
28.10 - prompt "Local tarballs directory"
28.11 - default ""
28.12 - help
28.13 - If you have previously downloaded the tarballs, enter the PATH where
28.14 - you stored them here.
28.15 -
28.16 -config SAVE_TARBALLS
28.17 - bool
28.18 - prompt "Save new tarballs"
28.19 - default n
28.20 - depends on LOCAL_TARBALLS_DIR != ""
28.21 - help
28.22 - If you say 'y' here, new downloaded tarballs will be saved in the
28.23 - directory you entered above.
28.24 -
28.25 -config PREFIX_DIR
28.26 - string
28.27 - prompt "Prefix directory"
28.28 - default "${HOME}/${CT_TARGET}"
28.29 - help
28.30 - This is the path the toolchain will run from.
28.31 -
28.32 -config INSTALL_DIR
28.33 - string
28.34 -# prompt "Install directory"
28.35 - default "${CT_PREFIX_DIR}"
28.36 -# help
28.37 -# This is the path the target will be installed into.
28.38 -#
28.39 -# Normally, you would set this to ${CT_PREFIX_DIR}, but if for some reasons
28.40 -# you can't write there, you can install somewhere else and have a third
28.41 -# person do the install for you.
28.42 -# The reason you might also want to install elsewhere is if you are going
28.43 -# to package your shinny new toolchain for distribution.
28.44 -
28.45 -config CUSTOM_PATCH
28.46 - bool
28.47 - prompt "Use custom patch directory"
28.48 - default n
28.49 - help
28.50 - If you have custom patches that you want to be applied, say 'Y' here and
28.51 - enter the path directory below.
28.52 -
28.53 - Note that you must ensure that the patch directory is arranged the same
28.54 - way the official directory is.
28.55 -
28.56 -config CUSTOM_PATCH_ONLY
28.57 - bool
28.58 - prompt "Only use custom patches"
28.59 - default n
28.60 - depends on CUSTOM_PATCH
28.61 - help
28.62 - Don't apply patches coming with crosstool-NG, only those patches available
28.63 - in the directory below.
28.64 -
28.65 - If you say 'N' here, then the patches provided with crosstool-NG will be
28.66 - applied first, and then your patches.
28.67 -
28.68 -config CUSTOM_PATCH_DIR
28.69 - string
28.70 - prompt "Custom patch directory"
28.71 - default ""
28.72 - depends on CUSTOM_PATCH
28.73 - help
28.74 - Enter the custom patch directory here.
28.75 -
28.76 -config REMOVE_DOCS
28.77 - bool
28.78 - prompt "Remove documentation"
28.79 - default n
28.80 - help
28.81 - Remove the installed documentation (man and info pages).
28.82 - Gains around 8MiB for a uClibc-based, C and C++ compiler.
28.83 -
28.84 -config INSTALL_DIR_RO
28.85 - bool
28.86 - prompt "Render the toolchain read-only"
28.87 - default n
28.88 - help
28.89 - Render the directory of the toolchain (and its sub-directories)
28.90 - read-only.
28.91 -
28.92 - Usefull for toolchains destined for production.