yann@445
|
1 |
# Options specific to crosstool-NG overall behavior
|
yann@1
|
2 |
|
yann@197
|
3 |
comment "crosstool-NG behavior"
|
yann@121
|
4 |
|
yann@244
|
5 |
config OBSOLETE
|
yann@244
|
6 |
bool
|
yann@244
|
7 |
prompt "Use obsolete features"
|
yann@244
|
8 |
help
|
yann@244
|
9 |
If you set this to Y, you will be able to select obsolete features.
|
yann@1300
|
10 |
|
yann@1300
|
11 |
Such obsolete features are the use of old kernel headers, old gcc
|
yann@1300
|
12 |
versions, etc... for which maintaining support in crosstool-NG
|
yann@1300
|
13 |
would be very costly.
|
yann@1300
|
14 |
|
yann@1300
|
15 |
It does not however mean that the specific feature or version has been
|
yann@1300
|
16 |
marked obsolete by the upstream team.
|
yann@244
|
17 |
|
yann@41
|
18 |
config EXPERIMENTAL
|
yann@41
|
19 |
bool
|
yann@41
|
20 |
prompt "Try features marked as EXPERIMENTAL"
|
yann@41
|
21 |
help
|
yann@41
|
22 |
If you set this to Y, then you will be able to try very experimental
|
yann@41
|
23 |
features.
|
yann@1300
|
24 |
|
yann@41
|
25 |
Experimental features can be one of:
|
yann@41
|
26 |
- working, in which case you should tell me it is!
|
yann@41
|
27 |
- buggy, in which case you could try patching and send me the result
|
yann@41
|
28 |
- unfinished, in which case you could try hacking it and send me the result
|
yann@384
|
29 |
- non-existant, in which case you could also try hacking it in and send me
|
yann@384
|
30 |
the result
|
yann@41
|
31 |
|
yann@3163
|
32 |
config ALLOW_BUILD_AS_ROOT
|
yann@3163
|
33 |
bool
|
yann@3163
|
34 |
prompt "Allow building as root user (READ HELP!)"
|
yann@3163
|
35 |
depends on EXPERIMENTAL
|
yann@3163
|
36 |
help
|
yann@3163
|
37 |
You normally do *not* need to be root to build a toolchain using
|
yann@3163
|
38 |
crosstool-NG. In fact, it is *VERY* dangerous to run as root, as
|
yann@3163
|
39 |
crosstool-NG will, as part of the build process, remove a few
|
yann@3163
|
40 |
directories. If anything goes wrong, running as root can ruin
|
yann@3163
|
41 |
your host distribution.
|
yann@3163
|
42 |
|
yann@3163
|
43 |
I can't stress it enough: DO NOT RUN AS ROOT !!
|
yann@3163
|
44 |
|
yann@3163
|
45 |
Do not run as root, you've been warned.
|
yann@3163
|
46 |
Do not come whining, if it nukes your host system.
|
yann@3163
|
47 |
Do not come whining, if you lose any data.
|
yann@3163
|
48 |
Do not run as root.
|
yann@3163
|
49 |
|
yann@3163
|
50 |
Do not run as root, you've been warned.
|
yann@3163
|
51 |
Do not come whining, if the Earth stops rotating.
|
yann@3163
|
52 |
Do not come whining, if kittens are smashed.
|
yann@3163
|
53 |
Do not run as root.
|
yann@3163
|
54 |
|
yann@3163
|
55 |
Do not run as root, do not run as root!
|
yann@3163
|
56 |
(ad libitum)
|
yann@3163
|
57 |
|
yann@3163
|
58 |
config ALLOW_BUILD_AS_ROOT_SURE
|
yann@3163
|
59 |
bool
|
yann@3163
|
60 |
prompt "Are you sure?"
|
yann@3163
|
61 |
depends on ALLOW_BUILD_AS_ROOT
|
yann@3163
|
62 |
|
yann@121
|
63 |
config DEBUG_CT
|
yann@121
|
64 |
bool
|
yann@121
|
65 |
prompt "Debug crosstool-NG"
|
yann@1867
|
66 |
depends on ! BACKEND
|
yann@121
|
67 |
help
|
yann@1300
|
68 |
Say 'y' here to get some options regarding debugging crosstool-NG.
|
yann@121
|
69 |
|
yann@121
|
70 |
if DEBUG_CT
|
yann@121
|
71 |
|
yann@725
|
72 |
config DEBUG_PAUSE_STEPS
|
yann@121
|
73 |
bool
|
yann@121
|
74 |
prompt "Pause between every steps"
|
yann@121
|
75 |
help
|
yann@121
|
76 |
Say 'y' if you intend to attend the build, and want to investigate
|
yann@121
|
77 |
the result of each steps before running the next one.
|
yann@121
|
78 |
|
yann@121
|
79 |
config DEBUG_CT_SAVE_STEPS
|
yann@121
|
80 |
bool
|
yann@121
|
81 |
prompt "Save intermediate steps"
|
yann@121
|
82 |
help
|
yann@121
|
83 |
If you say 'y' here, then you will be able to restart crosstool-NG at
|
yann@168
|
84 |
any step.
|
yann@1300
|
85 |
|
yann@1300
|
86 |
It is not currently possible to restart at any of the debug facilities.
|
yann@168
|
87 |
They are treated as a whole.
|
yann@1300
|
88 |
|
yann@2227
|
89 |
To get the full list os steps, run: ct-ng list-steps
|
yann@121
|
90 |
|
yann@121
|
91 |
config DEBUG_CT_SAVE_STEPS_GZIP
|
yann@121
|
92 |
bool
|
yann@121
|
93 |
prompt "gzip saved states"
|
yann@121
|
94 |
default y
|
yann@121
|
95 |
depends on DEBUG_CT_SAVE_STEPS
|
yann@121
|
96 |
help
|
yann@121
|
97 |
If you are tight on space, then you can ask to gzip the saved states
|
yann@121
|
98 |
tarballs. On the other hand, this takes some longer time...
|
yann@1300
|
99 |
|
yann@121
|
100 |
To lose as less time as possible, the gzip process is done with a low
|
yann@121
|
101 |
compression ratio (-3), which gives roughly 70% gain in size. Going
|
yann@121
|
102 |
further doesn't gain much, and takes far more time (believe me, I've
|
yann@121
|
103 |
got figures here! :-) ).
|
yann@121
|
104 |
|
yann@1064
|
105 |
config NO_OVERIDE_LC_MESSAGES
|
yann@1064
|
106 |
bool
|
yann@1064
|
107 |
prompt "Do *not* overide LC_MESSAGES (EXPERIMENTAL)"
|
yann@1064
|
108 |
depends on EXPERIMENTAL
|
yann@1064
|
109 |
help
|
yann@1064
|
110 |
By default, crosstool-NG sets and exports LC_ALL=C so that the
|
yann@1064
|
111 |
build.log file contains english messages, that can be read by
|
yann@1064
|
112 |
people most likely to help interpret the logs. If you say N here,
|
yann@1064
|
113 |
and your locale is not an english language, then dissecting your
|
yann@1064
|
114 |
log file will be difficult for most people but you.
|
yann@1064
|
115 |
|
yann@1064
|
116 |
If you say Y here, then your current locale settings will be used
|
yann@1064
|
117 |
to print messages, instead of plain english.
|
yann@1064
|
118 |
|
yann@1064
|
119 |
Say N, please.
|
yann@1064
|
120 |
|
yann@3083
|
121 |
config DEBUG_INTERACTIVE
|
yann@3083
|
122 |
bool
|
yann@3083
|
123 |
prompt "Interactive shell on failed commands"
|
yann@3083
|
124 |
help
|
yann@3083
|
125 |
If you say 'y' here, then an interactive shell will be spawned for
|
yann@3083
|
126 |
each failed command.
|
yann@3083
|
127 |
|
yann@3083
|
128 |
This shell will have the same environment that the failed command
|
yann@3083
|
129 |
was run with, and the working directory will be set to the directory
|
yann@3083
|
130 |
the failed command was run in.
|
yann@3083
|
131 |
|
yann@3083
|
132 |
After you fix the issue, you can exit the interactive shell with any
|
yann@3083
|
133 |
of these exit codes:
|
yann@3083
|
134 |
1 the issue was fixed, continue the build with the next command
|
yann@3083
|
135 |
2 the issue was fixed, re-run the failed command
|
yann@3083
|
136 |
3 abort the build
|
yann@3083
|
137 |
|
yann@3083
|
138 |
Note: '2' is only possible for commands run via CT_DoExecLog, though.
|
yann@3083
|
139 |
|
yann@121
|
140 |
endif
|