| Summary: | sys-libs/glibc-2.36-r6 installs pre-stripped files (false positive, see bug 793770) | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Agostino Sarubbo <ago> |
| Component: | Current packages | Assignee: | Gentoo Toolchain Maintainers <toolchain> |
| Status: | RESOLVED OBSOLETE | ||
| Severity: | normal | CC: | fturco, gentoo, gentoo, pacho |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| See Also: | https://bugs.gentoo.org/show_bug.cgi?id=830213 | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Bug Depends on: | 793770 | ||
| Bug Blocks: | |||
| Attachments: | build.log.xz | ||
|
Description
Agostino Sarubbo
2021-04-22 06:35:20 UTC
Created attachment 701583 [details]
build.log.xz
build log and emerge --info (compressed because it exceeds attachment limit, use 'xzless' to read it)
Happens here as well. """ * QA Notice: Pre-stripped files found: * /usr/lib64/crtn.o * /usr/lib/crtn.o """ Not immediately clear why, but these are .o files. Not .so files. Probably our stripping detection fails at them. Pre-strip detection happens at bin/estrip site around scanelf calls: https://gitweb.gentoo.org/proj/portage.git/tree/bin/estrip#n329 Might be binutils-2.36 related. Confirmed it's a portage's false positive and is triggered by binutils-2.36. The whole file has no symbols:
$ cat ../sysdeps/x86_64/crtn.S
.section .init,"ax",@progbits
addq $8, %rsp
ret
.section .fini,"ax",@progbits
addq $8, %rsp
ret
Executable reproducer:
$ x86_64-pc-linux-gnu-gcc -O2 -Wl,--defsym=__gentoo_check_ldflags__=0 ../sysdeps/x86_64/crtn.S -c -o crtn-2.36.o # -B/usr/x86_64-pc-linux-gnu/binutils-bin/2.35.2/
$ x86_64-pc-linux-gnu-gcc -O2 -Wl,--defsym=__gentoo_check_ldflags__=0 ../sysdeps/x86_64/crtn.S -c -o crtn-2.35.o -B/usr/x86_64-pc-linux-gnu/binutils-bin/2.35.2/
$ scanelf -yqRBF '#k%F' -k '!.symtab' crtn-2.35.o crtn-2.36.o
crtn-2.36.o
$ diff -U0 <(h readelf -W -S crtn-2.35.o) <(h readelf -W -S crtn-2.36.o)
--- /dev/fd/63 2021-06-01 22:59:09.056572177 +0100
+++ /dev/fd/62 2021-06-01 22:59:09.056572177 +0100
@@ -1 +1 @@
-There are 9 section headers, starting at offset 0x120:
+There are 8 section headers, starting at offset 0xc0:
@@ -11,3 +11,2 @@
- [ 6] .symtab SYMTAB 0000000000000000 000050 000090 18 7 6 8
- [ 7] .strtab STRTAB 0000000000000000 0000e0 000001 00 0 0 1
- [ 8] .shstrtab STRTAB 0000000000000000 0000e1 000038 00 0 0 1
+ [ 6] .note.gnu.property NOTE 0000000000000000 000050 000030 00 A 0 0 8
+ [ 7] .shstrtab STRTAB 0000000000000000 000080 00003b 00 0 0 1
Let's peek at 2.35's symtab:
$ readelf -W --symbols crtn-2.35.o
Symbol table '.symtab' contains 6 entries:
Num: Value Size Type Bind Vis Ndx Name
0: 0000000000000000 0 NOTYPE LOCAL DEFAULT UND
1: 0000000000000000 0 SECTION LOCAL DEFAULT 1
2: 0000000000000000 0 SECTION LOCAL DEFAULT 2
3: 0000000000000000 0 SECTION LOCAL DEFAULT 3
4: 0000000000000000 0 SECTION LOCAL DEFAULT 4
5: 0000000000000000 0 SECTION LOCAL DEFAULT 5
$ readelf -W --symbols crtn-2.36.o
<empty>
None of symbols look useful. I think it's reasonable to expect that for simple files .symtab might be absent.
Filed bug #784923 against portage. ci has reproduced this issue with version 2.33-r7 - Updating summary. ci has reproduced this issue with version 2.34-r1 - Updating summary. ci has reproduced this issue with version 2.34-r2 - Updating summary. ci has reproduced this issue with version 2.34-r3 - Updating summary. ci has reproduced this issue with version 2.34-r4 - Updating summary. ci has reproduced this issue with version 2.34-r6 - Updating summary. ci has reproduced this issue with version 2.34-r7 - Updating summary. ci has reproduced this issue with version 2.35 - Updating summary. ci has reproduced this issue with version 2.35-r1 - Updating summary. ci has reproduced this issue with version 2.35-r2 - Updating summary. ci has reproduced this issue with version 2.35-r3 - Updating summary. ci has reproduced this issue with version 2.35-r4 - Updating summary. *** Bug 840806 has been marked as a duplicate of this bug. *** ci has reproduced this issue with version 2.35-r5 - Updating summary. ci has reproduced this issue with version 2.35-r7 - Updating summary. ci has reproduced this issue with version 2.35-r8 - Updating summary. ci has reproduced this issue with version 2.35-r10 - Updating summary. ci has reproduced this issue with version 2.36-r3 - Updating summary. ci has reproduced this issue with version 2.36-r4 - Updating summary. ci has reproduced this issue with version 2.36-r5 - Updating summary. ci has reproduced this issue with version 2.36-r6 - Updating summary. Looks like this disappeared. |
