lsbcc/lsbc++ generates non-compliant binaries with GCC 4.5 and 4.6
Bug #1327291 reported by
Jeff Johnson
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| lsb |
In Progress
|
Medium
|
Unassigned | ||
| Mandriva |
In Progress
|
Medium
|
|||
Bug Description
When compiling shared object files, in some cases lsbcc and lsbc++ generate .so
files which brandelf reports to be of brand 'Linux' (3) rather than of brand
'SVR4' (0). These non-compliant shared object files seem to pass lsbappchk,
disturbingly, but prevent executables which have linked against them from
running when transported from a Linux Mint Debian Edition (LMDE) OS to a CentOS
5.8 OS. The error message of interest is "ELF file OS ABI invalid".
Debranding with brandelf results in missing symbols. The solution, for now,
seems to be to go back to GCC 4.4.
Perhaps lsbappchk's failure to catch this problem should be a separate bug?
| Changed in mandriva: | |
| importance: | Unknown → Medium |
| status: | Unknown → In Progress |
| tags: | added: elf |
| tags: | added: lsbcc |
To post a comment you must log in.
