Bug 174282 - [PATCH] 'find-requires' parses some objdump info incorrectly
Summary: [PATCH] 'find-requires' parses some objdump info incorrectly
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: redhat-rpm-config
Version: 4
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Jon Masters
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2005-11-27 09:35 UTC by Enrico Scholz
Modified: 2008-03-09 23:13 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2008-03-09 23:13:25 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Fixes 'find-requires' on ARM platforms (466 bytes, patch)
2005-11-27 09:35 UTC, Enrico Scholz
no flags Details | Diff

Description Enrico Scholz 2005-11-27 09:35:48 UTC
Description of problem:

Some platforms (e.g. arm) have additional data in objectfiles which
get reported by 'objdump' in a way like

| $ arm-xscale-linux-gnu-objdump -p /var/tmp/sessiondir-ensc.1126455583.ms4206/tmp/cross-arm-xscale-linux-gnu-glibc-2.3.6-1.1-root-ensc/usr/arm-xscale-linux-gnu/sys-root/lib/gconv/ISO8859-10.so 
| 
| /var/tmp/sessiondir-ensc.1126455583.ms4206/tmp/cross-arm-xscale-linux-gnu-glibc-2.3.6-1.1-root-ensc/usr/arm-xscale-linux-gnu/sys-root/lib/gconv/ISO8859-10.so:     file format elf32-littlearm
| 
| ...
| 
| Version References:
|   required from libc.so.6:
|     0x09691f73 0x00 04 GLIBC_2.1.3
|     0x0d696911 0x00 03 GLIBC_2.1
|     0x0d696910 0x00 02 GLIBC_2.0
| private flags = 2: [APCS-32] [FPA float format] [has entry point]

(note the 'private flags section')

This creates broken results like

| libc.so.6
| libc.so.6(2:)
| libc.so.6(GLIBC_2.0)

(note the 2nd line).

The attached patch fixes this.



Version-Release number of selected component (if applicable):

redhat-rpm-config-8.0.34-1.1

Comment 1 Enrico Scholz 2005-11-27 09:35:49 UTC
Created attachment 121517 [details]
Fixes 'find-requires' on ARM platforms

Comment 2 Christian Iseli 2007-01-20 00:59:14 UTC
This report targets the FC3 or FC4 products, which have now been EOL'd.

Could you please check that it still applies to a current Fedora release, and
either update the target product or close it ?

Thanks.

Comment 3 petrosyan 2008-03-09 23:13:25 UTC
Fedora Core 4 is no longer maintained.

Setting status to "INSUFFICIENT_DATA". If you can reproduce this bug in the
current Fedora release, please reopen this bug and assign it to the
corresponding Fedora version.


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