Bug 172161 - [RHEL4] Compilation problem: looking in /usr/lib instead of /usr/lib64
[RHEL4] Compilation problem: looking in /usr/lib instead of /usr/lib64
Status: CLOSED WORKSFORME
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: devhelp (Show other bugs)
4.0
x86_64 Linux
low Severity medium
: ---
: ---
Assigned To: Matthew Barnes
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2005-10-31 20:11 EST by Patrice Guay
Modified: 2008-02-29 08:10 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2008-02-29 08:10:48 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Patrice Guay 2005-10-31 20:11:30 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; fr; rv:1.7.12) Gecko/20050926 Red Hat/1.0.7-1.4.1.TL1 Firefox/1.0.7

Description of problem:
When compiling devhelp on the x86_64 architecture, compilation fails with this message:
/usr/lib/libpopt.so: could not read symbols: File in wrong format

This is simply due to the fact that the compiler is looking for libpopt.so in /usr/lib instead of /usr/lib64.


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

How reproducible:
Always

Steps to Reproduce:
1. rpm -Uvh http://updates.redhat.com/enterprise/4AS/en/os/SRPMS/devhelp-0.9.2-2.4.7.src.rpm
2. cd /usr/src/redhat/SPECS
3. rpmbuild -ba devhelp.spec


Actual Results:  Compilation aborts with the following message:
/usr/lib/libpopt.so: could not read symbols: File in wrong format

Expected Results:  Compilation should have completed without any error.

Additional info:
Comment 1 Patrice Guay 2005-10-31 20:18:49 EST
The same error applies to these packages:
gnome-games-2.8.0-4
gnome-mag-0.11.7-1
gnome-nettool-0.99.3-2
gnome-terminal-2.7.3-2
gnome-utils-2.8.0-5
gok-0.11.8-1
hal-0.4.2-1.EL4
librsvg2-2.8.1-1
Comment 2 Martin Stransky 2008-02-29 08:10:48 EST
I believe it's fixed now, right?

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