Bug 82363 - "pkg-config --libs blah" prints /usr/lib64 on Hammer
"pkg-config --libs blah" prints /usr/lib64 on Hammer
Status: CLOSED RAWHIDE
Product: Red Hat Raw Hide
Classification: Retired
Component: pkgconfig (Show other bugs)
1.0
x86_64 Linux
low Severity low
: ---
: ---
Assigned To: Havoc Pennington
: Triaged
Depends On:
Blocks: 79579
  Show dependency treegraph
 
Reported: 2003-01-21 12:15 EST by Joe Orton
Modified: 2008-05-01 11:38 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2003-02-24 23:21:19 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 Joe Orton 2003-01-21 12:15:49 EST
Description of problem:
"pkg-config --libs" output should not include /usr/lib64 on Hammer.

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

How reproducible:
Always

Steps to Reproduce:
e.g.
$ pkg-config --libs libxml-2.0
   
Actual results:
-L/usr/lib64 -lxml2 -lz -lm

Expected results:
 -lxml2 -lz -lm

Additional info:
A simple and probably naive fix is to pass the expansion of ${libdir} into
config.h, and check against that in pkg.c rather than the hard-coded "/usr/lib".
Comment 1 Havoc Pennington 2003-01-21 12:19:47 EST
Can you remind me why it removes -L/usr/lib? (I don't remember the impact of
this issue.)
Comment 2 Joe Orton 2003-01-21 12:25:00 EST
I think just because it changes the order the library search path unnecessarily:
so if I have "-L/usr/lib64 -L/home/joe/lib -lfoobar" then I might *want* to pick
up -lfoobar out of /home/joe/lib but the /usr/lib64 means I pick up the system
copy instead, if there is one.  It's not a big issue anyway.
Comment 3 Jeremy Katz 2003-02-24 23:21:19 EST
Nalin fixed this in 0.14.0-3

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