Bug 82363

Summary: "pkg-config --libs blah" prints /usr/lib64 on Hammer
Product: [Retired] Red Hat Raw Hide Reporter: Joe Orton <jorton>
Component: pkgconfigAssignee: Havoc Pennington <hp>
Status: CLOSED RAWHIDE QA Contact:
Severity: low Docs Contact:
Priority: low    
Version: 1.0Keywords: Triaged
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2003-02-25 04:21:19 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On:    
Bug Blocks: 79579    

Description Joe Orton 2003-01-21 17:15:49 UTC
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 17:19:47 UTC
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 17:25:00 UTC
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-25 04:21:19 UTC
Nalin fixed this in 0.14.0-3