ExternalVendorCode/crosstool-ng
1
0
Fork 0
mirror of https://github.com/crosstool-ng/crosstool-ng.git synced 2024-12-29 00:58:51 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity
19fdf86ab6
crosstool-ng/config/global/ct-behave.in

141 lines
4.7 KiB
Plaintext
Raw Normal View History

Break-down config/global.in into smaller, much more maintainable files. config/paths.in | 419 1 418 0 -------------------------------------------------------- 1 file changed, 1 insertion(+), 418 deletions(-)
2008-04-17 20:02:07 +00:00
# Options specific to crosstool-NG overall behavior
comment "crosstool-NG behavior"
config OBSOLETE
bool
prompt "Use obsolete features"
help
If you set this to Y, you will be able to select obsolete features.
Add a bit more explanations on the meaning of OBSOLETE and EXPERIMENTAL. -------- diffstat follows -------- /trunk/config/global/ct-behave.in | 22 13 9 0 +++++++++++++--------- /trunk/docs/overview.txt | 8 6 2 0 ++++++-- 2 files changed, 19 insertions(+), 11 deletions(-)
2009-04-20 21:30:25 +00:00
Such obsolete features are the use of old kernel headers, old gcc
versions, etc... for which maintaining support in crosstool-NG
would be very costly.
It does not however mean that the specific feature or version has been
marked obsolete by the upstream team.
Break-down config/global.in into smaller, much more maintainable files. config/paths.in | 419 1 418 0 -------------------------------------------------------- 1 file changed, 1 insertion(+), 418 deletions(-)
2008-04-17 20:02:07 +00:00
config EXPERIMENTAL
bool
prompt "Try features marked as EXPERIMENTAL"
help
If you set this to Y, then you will be able to try very experimental
features.
Add a bit more explanations on the meaning of OBSOLETE and EXPERIMENTAL. -------- diffstat follows -------- /trunk/config/global/ct-behave.in | 22 13 9 0 +++++++++++++--------- /trunk/docs/overview.txt | 8 6 2 0 ++++++-- 2 files changed, 19 insertions(+), 11 deletions(-)
2009-04-20 21:30:25 +00:00
Break-down config/global.in into smaller, much more maintainable files. config/paths.in | 419 1 418 0 -------------------------------------------------------- 1 file changed, 1 insertion(+), 418 deletions(-)
2008-04-17 20:02:07 +00:00
Experimental features can be one of:
- working, in which case you should tell me it is!
- buggy, in which case you could try patching and send me the result
- unfinished, in which case you could try hacking it and send me the result
- non-existant, in which case you could also try hacking it in and send me
the result
scripts: check for running as root Running as root is really, really dangerous. Add a runtime-check that refuses to build if running as root. Can be overriden with a double switch in the menuconfig. Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
2013-01-10 21:38:48 +00:00
config ALLOW_BUILD_AS_ROOT
bool
prompt "Allow building as root user (READ HELP!)"
depends on EXPERIMENTAL
help
You normally do *not* need to be root to build a toolchain using
crosstool-NG. In fact, it is *VERY* dangerous to run as root, as
crosstool-NG will, as part of the build process, remove a few
directories. If anything goes wrong, running as root can ruin
your host distribution.
I can't stress it enough: DO NOT RUN AS ROOT !!
Do not run as root, you've been warned.
Do not come whining, if it nukes your host system.
Do not come whining, if you lose any data.
Do not run as root.
Do not run as root, you've been warned.
Do not come whining, if the Earth stops rotating.
Do not come whining, if kittens are smashed.
Do not run as root.
Do not run as root, do not run as root!
(ad libitum)
config ALLOW_BUILD_AS_ROOT_SURE
bool
prompt "Are you sure?"
depends on ALLOW_BUILD_AS_ROOT
Break-down config/global.in into smaller, much more maintainable files. config/paths.in | 419 1 418 0 -------------------------------------------------------- 1 file changed, 1 insertion(+), 418 deletions(-)
2008-04-17 20:02:07 +00:00
config DEBUG_CT
bool
prompt "Debug crosstool-NG"
config: hide options to debug crosstool-NG when a backend When used as a backend, it does not make sense to debug crosstool-NG, so hide the option.
2010-03-29 08:03:29 +00:00
depends on ! BACKEND
Break-down config/global.in into smaller, much more maintainable files. config/paths.in | 419 1 418 0 -------------------------------------------------------- 1 file changed, 1 insertion(+), 418 deletions(-)
2008-04-17 20:02:07 +00:00
help
Add a bit more explanations on the meaning of OBSOLETE and EXPERIMENTAL. -------- diffstat follows -------- /trunk/config/global/ct-behave.in | 22 13 9 0 +++++++++++++--------- /trunk/docs/overview.txt | 8 6 2 0 ++++++-- 2 files changed, 19 insertions(+), 11 deletions(-)
2009-04-20 21:30:25 +00:00
Say 'y' here to get some options regarding debugging crosstool-NG.
Break-down config/global.in into smaller, much more maintainable files. config/paths.in | 419 1 418 0 -------------------------------------------------------- 1 file changed, 1 insertion(+), 418 deletions(-)
2008-04-17 20:02:07 +00:00
if DEBUG_CT
Hmmm. The debug pause at each step never ever worked... Sigh... /trunk/scripts/crosstool.sh | 2 1 1 0 +- /trunk/config/global/ct-behave.in | 2 1 1 0 +- 2 files changed, 2 insertions(+), 2 deletions(-)
2008-07-25 22:57:35 +00:00
config DEBUG_PAUSE_STEPS
Break-down config/global.in into smaller, much more maintainable files. config/paths.in | 419 1 418 0 -------------------------------------------------------- 1 file changed, 1 insertion(+), 418 deletions(-)
2008-04-17 20:02:07 +00:00
bool
prompt "Pause between every steps"
help
Say 'y' if you intend to attend the build, and want to investigate
the result of each steps before running the next one.
config DEBUG_CT_SAVE_STEPS
bool
prompt "Save intermediate steps"
help
If you say 'y' here, then you will be able to restart crosstool-NG at
any step.
Add a bit more explanations on the meaning of OBSOLETE and EXPERIMENTAL. -------- diffstat follows -------- /trunk/config/global/ct-behave.in | 22 13 9 0 +++++++++++++--------- /trunk/docs/overview.txt | 8 6 2 0 ++++++-- 2 files changed, 19 insertions(+), 11 deletions(-)
2009-04-20 21:30:25 +00:00
It is not currently possible to restart at any of the debug facilities.
Break-down config/global.in into smaller, much more maintainable files. config/paths.in | 419 1 418 0 -------------------------------------------------------- 1 file changed, 1 insertion(+), 418 deletions(-)
2008-04-17 20:02:07 +00:00
They are treated as a whole.
Add a bit more explanations on the meaning of OBSOLETE and EXPERIMENTAL. -------- diffstat follows -------- /trunk/config/global/ct-behave.in | 22 13 9 0 +++++++++++++--------- /trunk/docs/overview.txt | 8 6 2 0 ++++++-- 2 files changed, 19 insertions(+), 11 deletions(-)
2009-04-20 21:30:25 +00:00
docs: overview.txt is gone, point to the new documentation Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
2010-12-21 23:34:56 +00:00
To get the full list os steps, run: ct-ng list-steps
Break-down config/global.in into smaller, much more maintainable files. config/paths.in | 419 1 418 0 -------------------------------------------------------- 1 file changed, 1 insertion(+), 418 deletions(-)
2008-04-17 20:02:07 +00:00
config DEBUG_CT_SAVE_STEPS_GZIP
bool
prompt "gzip saved states"
default y
depends on DEBUG_CT_SAVE_STEPS
help
If you are tight on space, then you can ask to gzip the saved states
tarballs. On the other hand, this takes some longer time...
Add a bit more explanations on the meaning of OBSOLETE and EXPERIMENTAL. -------- diffstat follows -------- /trunk/config/global/ct-behave.in | 22 13 9 0 +++++++++++++--------- /trunk/docs/overview.txt | 8 6 2 0 ++++++-- 2 files changed, 19 insertions(+), 11 deletions(-)
2009-04-20 21:30:25 +00:00
Break-down config/global.in into smaller, much more maintainable files. config/paths.in | 419 1 418 0 -------------------------------------------------------- 1 file changed, 1 insertion(+), 418 deletions(-)
2008-04-17 20:02:07 +00:00
To lose as less time as possible, the gzip process is done with a low
compression ratio (-3), which gives roughly 70% gain in size. Going
further doesn't gain much, and takes far more time (believe me, I've
got figures here! :-) ).
Overide locale to C so as to have readable logs. Offer a DEBUG & EXPERIMENTAL setting to not overide locale. /trunk/scripts/crosstool.sh | 10 7 3 0 +++++++--- /trunk/config/global/ct-behave.in | 17 17 0 0 +++++++++++++++++ 2 files changed, 24 insertions(+), 3 deletions(-)
2008-11-20 17:48:10 +00:00
config NO_OVERIDE_LC_MESSAGES
bool
prompt "Do *not* overide LC_MESSAGES (EXPERIMENTAL)"
depends on EXPERIMENTAL
help
By default, crosstool-NG sets and exports LC_ALL=C so that the
build.log file contains english messages, that can be read by
people most likely to help interpret the logs. If you say N here,
and your locale is not an english language, then dissecting your
log file will be difficult for most people but you.
If you say Y here, then your current locale settings will be used
to print messages, instead of plain english.
Say N, please.
scripts: add option to start an interactive debug shell Add an option that, when a command fails: - starts an interactive shell with the failed command's environment - attempts re-execution of the failed command, continues, or aborts at user's whim. Before starting the debug-shell, the backtrace is printed. When exiting for an abort, the standard error message is printed. Based on an idea and a patch from: Johannes Stezenbach <js@sig21.net> http://sourceware.org/ml/crossgcc/2012-09/msg00144.html Signed-off-by: Johannes Stezenbach <js@sig21.net> [yann.morin.1998@free.fr: integrate in the fault handler] Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Acked-by: Johannes Stezenbach <js@sig21.net> Patchwork-Id: 191571 Patchwork-Id: 191668
2012-10-06 21:48:07 +00:00
config DEBUG_INTERACTIVE
bool
prompt "Interactive shell on failed commands"
help
If you say 'y' here, then an interactive shell will be spawned for
each failed command.
This shell will have the same environment that the failed command
was run with, and the working directory will be set to the directory
the failed command was run in.
After you fix the issue, you can exit the interactive shell with any
of these exit codes:
1 the issue was fixed, continue the build with the next command
2 the issue was fixed, re-run the failed command
3 abort the build
Note: '2' is only possible for commands run via CT_DoExecLog, though.
Break-down config/global.in into smaller, much more maintainable files. config/paths.in | 419 1 418 0 -------------------------------------------------------- 1 file changed, 1 insertion(+), 418 deletions(-)
2008-04-17 20:02:07 +00:00
endif
Reference in New Issue Copy Permalink