Commit
b80a6b900f743582c3ebb9bd29494959c2b9e66c
by Helmut Grohne
improve usage of dpkg-architecture
* Properly quote arguments, which also makes shellcheck a little happier. * Use the -i flag rather than matching its output. * When in a hook, prefer the hook argument as architecture.
Commit
7b6b07bfa607abea2da0f7aaeb34c758c03e4f37
by Helmut Grohne
unconditionally apply patch_gcc_has_include_next
gcc-12 builds started failing in stage1 while compiling libgcov-merge.c due to missing <sys/mman.h>. That header is only available in glibc stage2, so the issue is that HAVE_SYS_MMAN_H is defined. That happens, because the relevant configure check erroneously succeeds by using /lib/cpp rather than the correct cpp invocation. cpp is misdetected, because the correct cpp failed #including <limits.h>, because our patched __has_include_next(<limits.h>) produces an error, which is gcc bug 80755 and is fixed by this very patch. A subtle change in include directory order made this patch important and the failure came three layers later.
Commit
cacf3bf31cd1ecffb4e44db9e4a902242964c8a6
by Helmut Grohne
increase shellcheck happiness
These are relatively obvious fixes that e.g. improve compatibility with bash, add missing quoting or use idiomatic computations.
What remains for shellcheck largely is style remarks and false positives. For instance, we excessively modify variables in subshells to intentionally get those changes reverted. Likewise, using variables in single-quoted strings is not a mistake. In order to address the globbing issues, more architectural changes would be necessary.
Commit
00b0af3691757d636731dadb66e0294c062e5820
by Helmut Grohne
adapt to linux-libc-dev having become a:all+m-a:foreign
Most of the time, we no longer have to rebuild linux-libc-dev. Sometimes, it's missing headers though and then we need to rebuild it, but not as a cross build, but an indep-only build.
Commit
916611197b58b972dbcba7802bc15a56d5d2c48b
by Helmut Grohne
rewrite wdotap patch set on top of gcc-for-host changes
The merging of gcc-for-host caused a lot of changes to the gcc packaging and made the wdotap patch set from cross-gcc-dev no longer work. It required significant changes and quite some aspects could be dropped resulting in a much smaller patch that is inlined in rebootstrap for now. We'll see whether that works better or worse.
Commit
395be9dfc0f9f70d27a4711fa58eed16418f1a04
by Helmut Grohne
linux: always regenerate d/control
Since linux-libc-dev is arch:all now, we only have two cases. Either the one in the archive is good enough or we get to build it. When we build it, we bump the version. When we bump the version, we must regenerate d/control (changed in src:linux).