Debug: Add verbosity to cmake (LLVM) and make (Linux) options

Last weekend I finished a marathon in building a ThinLTO and PGO optimized LLVM toolchain - optimized here means for Linux v5.9-rc2 with Clang-CFI enabled (details see [0] and especially my request on this one here in [1]).

While gasping at the the following section:

==  Building kernels  ==
========================

+ for TARGET in "${TARGETS[@]}"
+ case ${TARGET} in
+ make -skj4 O=out LLVM=1 distclean defconfig bzImage modules

real    45m56.082s
user    166m53.758s
sys     8m11.487s

$ du -s -m ~/src/linux-kernel/git/out
540     /home/dileks/src/linux-kernel/git/out

Several minutes you do not get a feedback.

For me watching the make V=1 lines of a Linux-kernel build is psychologically fundamental - it calms me down - and besides helpful to see what’s going on and warnings etc.

Same can be done for cmake and the LLVM build-process (where I am personally and psychologically not interested).

Can we rename Building kernels to Building Linux and remove the double space to be consistent with the other section names?

$ grep '^\==  Building' log_tc-build.txt
==  Building kernels  ==

$ grep '^\== Building' log_tc-build.txt
== Building LLVM stage 1 ==
== Building LLVM stage 2 ==
== Building PGO profiles ==
== Building LLVM stage 3 ==

Side-note: Shouldn’t this be named “Generating PGO profiles”?

[0] https://github.com/ClangBuiltLinux/tc-build/issues/109 [1] https://github.com/ClangBuiltLinux/tc-build/issues/109#issuecomment-683355211 [2] https://github.com/samitolvanen/linux/commits/clang-cfi

[msfjarvis]

Well,

Short answer

Longer answer: Building the kernel is a profiling task, and what goes on during the actual build is inconsequential in the grand scheme of things: building a Clang compiler. I can’t answer for your psychological requirements, but to keep track of what’s happening in the kernel build you can simply use htop to monitor make calls. What you’re looking for is an extremely niche requirement that’s not useful to other tc-build users so I’d recommend simply carrying a local patch for make V=1 if its important to you. I’ll look into the formatting issues.

[msfjarvis]

#115 has been filed for the formatting fixes, there is not going to be a debug option in the scripts so I’m closing this issue as resolved.