http://arm.koji.fedoraproject.org/koji/taskinfo?taskID=1466963 section [ 5] '.dynsym': symbol 18: st_value out of bounds section [38] '.symtab': symbol 318: st_value out of bounds *** failure in ../src/elflint --quiet --gnu-ld ../src/nm section [38] '.symtab': symbol 255: st_value out of bounds *** failure in ../src/elflint --quiet --gnu-ld ../src/objdump section [ 5] '.dynsym': symbol 91: st_value out of bounds section [38] '.symtab': symbol 529: st_value out of bounds *** failure in ../src/elflint --quiet --gnu-ld ../src/readelf section [36] '.symtab': symbol 122: st_value out of bounds *** failure in ../src/elflint --quiet --gnu-ld ../src/size section [38] '.symtab': symbol 292: st_value out of bounds *** failure in ../src/elflint --quiet --gnu-ld ../src/strip FAIL: run-elflint-self.sh
That is caused by: 0.155-4 Replace elfutils-0.155-binutils-pr-ld-13621.patch with upstream fix. In the worst case we can go back to the previous hack. But that hides other problems. Could someone upload the problematic binaries (src/size is probably the smallest) from a native arm build? So we can inspect which symbol it really is that causes trouble?
Got access to an arm system (f18, armv7hl.tegra, gcc 4.7.2-8, binutils-2.23.51.0.1-3.fc18.armv7hl). Looks like the issue is that arm is using the symbol name "__bss_start__" instead of "__bss_start" Only "__bss_start" is handled specially by eu-elflint --gnu. https://lists.fedorahosted.org/pipermail/elfutils-devel/2013-February/002967.html
Fixed in elfutils-0.155-5.fc19: - Add ARM variant to elfutils-0.155-binutils-pr-ld-13621.patch rhbz#914908.
elfutils-0.156-3.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/elfutils-0.156-3.fc19
elfutils-0.156-3.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.