When dumping the DokuWiki table of samples, don't leave the kernel headers version empty if using a custom headers set., and say so.
/trunk/scripts/showSamples.sh | 6 5 1 0 +++++-
1 file changed, 5 insertions(+), 1 deletion(-)
1 # Options specific to logging
7 prompt "Maximum log level to see:"
8 default LOG_INFO if !DEBUG_CT
9 default LOG_DEBUG if DEBUG_CT
15 The build will be silent.
16 Only if there is an error will you see a message.
22 The same as above, plus warnings.
28 The same as above, plus informational messages (main steps).
34 The same as above, plus extra messages (sub-steps).
40 The same as above, plus lots of crosstool-NG debug information.
46 The same as above, plus all components build messages (very noisy!).
52 default "ERROR" if LOG_ERROR
53 default "WARN" if LOG_WARN
54 default "INFO" if LOG_INFO
55 default "EXTRA" if LOG_EXTRA
56 default "DEBUG" if LOG_DEBUG
57 default "ALL" if LOG_ALL
59 config LOG_SEE_TOOLS_WARN
61 prompt "Warnings from the tools' builds"
63 depends on ! LOG_ERROR
65 Treat warnings from the different tools as crosstool-NG warnings.
66 If you say 'y' here, then those warnings will be prefixed with
67 '[WARN ]' instead of the default '[ALL ]'.
69 You can safely say 'n' here. Those warnings will anyway be
70 recorded in the log file (provided you configured one).
72 Tools error will always be logged as crosstool-NG errors.
74 config LOG_PROGRESS_BAR
80 If you say 'y' here, you'll be able to see the elapsed time.
82 As a bonus, you'll also get a rotating bar (/-\|) showing you
83 that the build is not stalled (the bar rotates 1/4 every 10 lines
84 of components build log).
86 Note that the elapsed time can stall for a little while if a
87 component has long commands, as the elapsed time is only updated
92 prompt "Log to a file"
95 Save *full* logs to a file. Even log levels you didn't specify above
96 will be available in this file. The log file will be named build.log
97 and stored in the toolchain prefix dir (set above).
99 As a bonus, there is a script in tools/extractConfig.sh that is able
100 to extract the configuration of crosstool-NG from the log file.
104 config LOG_FILE_COMPRESS
106 prompt "Compress the log file"
108 depends on LOG_TO_FILE
110 Compress the log file once the toolchain is successfully built.