Bug 1318714 - FTBFS on mips and mipsel (test run-strip-strmerge.sh fails)
Summary: FTBFS on mips and mipsel (test run-strip-strmerge.sh fails)
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: elfutils
Version: 25
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Mark Wielaard
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-17 15:03 UTC by Laurent Bigonville
Modified: 2017-12-12 10:57 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-12-12 10:57:22 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Laurent Bigonville 2016-03-17 15:03:19 UTC
Hi,

On debian, it seems that elfutils FTBFS on mips and mipsel architectures due to the run-strip-strmerge.sh test:

FAIL: run-strip-strmerge.sh
===========================

elflint /«PKGBUILDDIR»/tests/elfstrmerge
invalid machine flags: 0x70001007
program header entry 2: unknown program header entry type 0x70000003
program header entry 3: unknown program header entry type 0x70000000
section [ 3] '.MIPS.abiflags' has unsupported type 1879048234
section [ 4] '.reginfo' has unsupported type 1879048198
section [ 6] '.dynamic': entry 14: unknown tag
section [ 6] '.dynamic': entry 15: unknown tag
section [ 6] '.dynamic': entry 18: unknown tag
section [ 6] '.dynamic': entry 19: unknown tag
section [ 6] '.dynamic': entry 20: unknown tag
section [ 6] '.dynamic': entry 21: unknown tag
section [ 6] '.dynamic': entry 22: unknown tag
section [ 6] '.dynamic': entry 23: unknown tag
section [ 6] '.dynamic': entry 24: unknown tag
section [ 8] '.dynsym': symbol 2: non-local section symbol
section [23] '.got' contains invalid processor-specific flag(s) 0x10000000
section [24] '.sdata' contains invalid processor-specific flag(s) 0x10000000
section [28] '.debug_aranges' has wrong type: expected PROGBITS, is SHT_LOPROC+1e
section [28] '.debug_aranges' has unsupported type 1879048222
section [29] '.debug_info' has wrong type: expected PROGBITS, is SHT_LOPROC+1e
section [29] '.debug_info' has unsupported type 1879048222
section [30] '.debug_abbrev' has wrong type: expected PROGBITS, is SHT_LOPROC+1e
section [30] '.debug_abbrev' has unsupported type 1879048222
section [31] '.debug_line' has wrong type: expected PROGBITS, is SHT_LOPROC+1e
section [31] '.debug_line' has unsupported type 1879048222
section [32] '.debug_frame' has wrong type: expected PROGBITS, is SHT_LOPROC+1e
section [32] '.debug_frame' has unsupported type 1879048222
section [33] '.debug_str' has wrong type: expected PROGBITS, is SHT_LOPROC+1e
section [33] '.debug_str' has unsupported type 1879048222
section [34] '.debug_loc' has wrong type: expected PROGBITS, is SHT_LOPROC+1e
section [34] '.debug_loc' has unsupported type 1879048222
section [35] '.debug_ranges' has wrong type: expected PROGBITS, is SHT_LOPROC+1e
section [35] '.debug_ranges' has unsupported type 1879048222
section [36] '.gnu.attributes': offset 15: unrecognized attribute tag 4
section [39] '.symtab': symbol 85: st_value out of bounds
section [39] '.symtab': symbol 89: non-local section symbol
section [39] '.symtab': symbol 157: st_value out of bounds
FAIL run-strip-strmerge.sh (exit status: 1)





https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818485

Comment 2 Mark Wielaard 2016-03-17 15:33:08 UTC
Note that the mips backend hasn't been submitted upstream and so it Debian only.

Those errors come from elflint, which is run after the actual strmerge test to see if the resulting ELF file looks sane.

Apparently MIPS has a couple of things elflint doesn't know about.

It would be nice if someone who knows MIPS would help create a proper backend for it upstream.

Comment 3 Jan Kurik 2016-07-26 04:39:28 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 25 development cycle.
Changing version to '25'.

Comment 4 Fedora End Of Life 2017-11-16 18:41:44 UTC
This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '25'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 25 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 5 Fedora End Of Life 2017-12-12 10:57:22 UTC
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.