Bug 792984 – sys-libs/libstdc++-v3-3.3.6-r4 calls objdump directly

• Status: CONFIRMED
• Product: Gentoo Linux

[Description Agostino Sarubbo 2021-05-30 09:33:41 UTC]

https://blogs.gentoo.org/ago/2020/07/04/gentoo-tinderbox/

Issue: sys-libs/libstdc++-v3-3.3.6-r3 calls objdump directly.
Discovered on: amd64 (internal ref: ci)

NOTE:
This machine uses GCC-11: https://gcc.gnu.org/gcc-11/porting_to.html
As per QA policy, toolchain tools must not be called directly because they can cause issue in cross-compiling and because is not possible use a different OBJDUMP implementation (like llvm-objdump). To reproduce, please use sys-devel/gcc-config[-native-symlinks], sys-devel/binutils-config[-native-symlinks].

[Comment 1 Agostino Sarubbo 2021-05-30 09:33:43 UTC]

CC'ing also the author of the commit (072701a499b6195a51955f8357248d566f1e25b2)

[Comment 2 Agostino Sarubbo 2021-05-30 09:33:45 UTC]

Created attachment 712488 [details]
build.log

build log and emerge --info

[Comment 3 Agostino Sarubbo 2021-05-30 09:33:47 UTC]

Possible context of error(s):

checking assembler subsection support... /var/tmp/portage/sys-libs/libstdc++-v3-3.3.6-r3/work/gcc-3.3.6/gcc/configure: line 7213: nm: command not found
checking linker read-only and read-write section mixing... /var/tmp/portage/sys-libs/libstdc++-v3-3.3.6-r3/work/gcc-3.3.6/gcc/configure: line 8110: objdump: command not found
make[1]: ar: No such file or directory
/var/tmp/portage/sys-libs/libstdc++-v3-3.3.6-r3/work/gcc-3.3.6/gcc/configure: line 7214: nm: command not found

[Comment 4 Agostino Sarubbo 2022-08-04 06:46:03 UTC]

ci has reproduced this issue with version 3.3.6-r4 - Updating summary.