yann@445: # Options specific to crosstool-NG overall behavior
yann@1: 
yann@197: comment "crosstool-NG behavior"
yann@121: 
yann@244: config OBSOLETE
yann@244:     bool
yann@244:     prompt "Use obsolete features"
yann@244:     help
yann@244:       If you set this to Y, you will be able to select obsolete features.
yann@1300:       
yann@1300:       Such obsolete features are the use of old kernel headers, old gcc
yann@1300:       versions, etc... for which maintaining support in crosstool-NG
yann@1300:       would be very costly.
yann@1300:       
yann@1300:       It does not however mean that the specific feature or version has been
yann@1300:       marked obsolete by the upstream team.
yann@244: 
yann@41: config EXPERIMENTAL
yann@41:     bool
yann@41:     prompt "Try features marked as EXPERIMENTAL"
yann@41:     help
yann@41:       If you set this to Y, then you will be able to try very experimental
yann@41:       features.
yann@1300:       
yann@41:       Experimental features can be one of:
yann@41:         - working, in which case you should tell me it is!
yann@41:         - buggy, in which case you could try patching and send me the result
yann@41:         - unfinished, in which case you could try hacking it and send me the result
yann@384:         - non-existant, in which case you could also try hacking it in and send me
yann@384:           the result
yann@41: 
yann@121: config DEBUG_CT
yann@121:     bool
yann@121:     prompt "Debug crosstool-NG"
yann@1867:     depends on ! BACKEND
yann@121:     help
yann@1300:       Say 'y' here to get some options regarding debugging crosstool-NG.
yann@121: 
yann@121: if DEBUG_CT
yann@121: 
yann@725: config DEBUG_PAUSE_STEPS
yann@121:     bool
yann@121:     prompt "Pause between every steps"
yann@121:     help
yann@121:       Say 'y' if you intend to attend the build, and want to investigate
yann@121:       the result of each steps before running the next one.
yann@121: 
yann@121: config DEBUG_CT_SAVE_STEPS
yann@121:     bool
yann@121:     prompt "Save intermediate steps"
yann@121:     help
yann@121:       If you say 'y' here, then you will be able to restart crosstool-NG at
yann@168:       any step.
yann@1300:       
yann@1300:       It is not currently possible to restart at any of the debug facilities.
yann@168:       They are treated as a whole.
yann@1300:       
yann@2227:       To get the full list os steps, run: ct-ng list-steps
yann@121: 
yann@121: config DEBUG_CT_SAVE_STEPS_GZIP
yann@121:     bool
yann@121:     prompt "gzip saved states"
yann@121:     default y
yann@121:     depends on DEBUG_CT_SAVE_STEPS
yann@121:     help
yann@121:       If you are tight on space, then you can ask to gzip the saved states
yann@121:       tarballs. On the other hand, this takes some longer time...
yann@1300:       
yann@121:       To lose as less time as possible, the gzip process is done with a low
yann@121:       compression ratio (-3), which gives roughly 70% gain in size. Going
yann@121:       further doesn't gain much, and takes far more time (believe me, I've
yann@121:       got figures here! :-) ).
yann@121: 
yann@1064: config NO_OVERIDE_LC_MESSAGES
yann@1064:     bool
yann@1064:     prompt "Do *not* overide LC_MESSAGES (EXPERIMENTAL)"
yann@1064:     depends on EXPERIMENTAL
yann@1064:     help
yann@1064:       By default, crosstool-NG sets and exports LC_ALL=C so that the
yann@1064:       build.log file contains english messages, that can be read by
yann@1064:       people most likely to help interpret the logs. If you say N here,
yann@1064:       and your locale is not an english language, then dissecting your
yann@1064:       log file will be difficult for most people but you.
yann@1064:       
yann@1064:       If you say Y here, then your current locale settings will be used
yann@1064:       to print messages, instead of plain english.
yann@1064:       
yann@1064:       Say N, please.
yann@1064: 
yann@3083: config DEBUG_INTERACTIVE
yann@3083:     bool
yann@3083:     prompt "Interactive shell on failed commands"
yann@3083:     help
yann@3083:       If you say 'y' here, then an interactive shell will be spawned for
yann@3083:       each failed command.
yann@3083:       
yann@3083:       This shell will have the same environment that the failed command
yann@3083:       was run with, and the working directory will be set to the directory
yann@3083:       the failed command was run in.
yann@3083:       
yann@3083:       After you fix the issue, you can exit the interactive shell with any
yann@3083:       of these exit codes:
yann@3083:         1  the issue was fixed, continue the build with the next command
yann@3083:         2  the issue was fixed, re-run the failed command
yann@3083:         3  abort the build
yann@3083:       
yann@3083:       Note: '2' is only possible for commands run via CT_DoExecLog, though.
yann@3083: 
yann@121: endif