550302c0b9
With BR2_RELRO_PARTIAL or BR2_RELRO_FULL, our toolchain wrapper will forcibly add -Wl,-z,relro to any call to the actual compiler. This usually works OK, because gcc will only use those options it needs for the compile step it has to carry: pre-processing, compiling, assembling, or linking, and ignore those options it does not need. Excpt in one case: when -v is passed standalone, with no input file, then gcc will falsely believe it has to do a link stage; $ gcc -Wl,-z,relro -v [...] /usr/bin/ld: /usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/Scrt1.o: in function `_start': (.text+0x24): undefined reference to `main' collect2: error: ld returned 1 exit status Fixing that in our wrapper will not be easy, because we'd have to detect there is no input file. Doing so would probably require we support almost all gcc options to differentiate between the parameter of an option (e.g. -I /some/path) from an actual inpout file. This would not be very robust, and would have a high risk od breaking when we introduce the next gcc version. Since it seems that only rhash is affected, due to its inventive, custom, hand-written configure script, we just patch it to be a bit more robust in the face of a compiler that could not accept -v, and fallback to --version. Fixes: - http://autobuild.buildroot.org/results/8605c16cc28316954ce8b9dcc266974390c5da20 Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com> [yann.morin.1998@free.fr: - retain "$CC -v" as default, fallback to "$CC --version", in the hope that it stands better chance with upstream - write a commit log to explain the actual root-cause of the build failure ] Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr> |
||
---|---|---|
.. | ||
0001-configure-allow-cross-compilation.patch | ||
Config.in | ||
rhash.hash | ||
rhash.mk |