Bug 147678

Summary: gsl-config --libs produces wrong output
Product: Red Hat Enterprise Linux 4 Reporter: Martins Innus <minnus>
Component: gslAssignee: Ivana Varekova <varekova>
Status: CLOSED ERRATA QA Contact: David Lawrence <dkl>
Severity: medium Docs Contact:
Priority: medium    
Version: 4.0   
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: RHBA-2005-172 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2005-06-09 12:18:13 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Martins Innus 2005-02-10 15:27:40 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6)
Gecko/20040612 Firefox/0.8

Description of problem:
The gsl-1.1-nousr.patch patch in this package messes up the gsl-config
--libs command under x86_64. The offending lines:

-               echo @GSL_LIBS@ $GSL_CBLAS_LIB -lm
+               echo @GSL_LIBS@ $GSL_CBLAS_LIB -lm | sed "s|-L/usr/lib||g"


Cause the following output:

[minnus@zappa SOURCES]$ gsl-config --libs
64 -lgsl -lgslcblas -lm

The "64" being left over from -L/usr/lib64, where the rest was
stripped out by the above "sed" command.

Version-Release number of selected component (if applicable):
gsl-devel-1.5-1

How reproducible:
Always

Steps to Reproduce:
1.gsl-config --libs
2.
3.
    

Actual Results:  64 -lgsl -lgslcblas -lm

Expected Results:  -lgsl -lgslcblas -lm

or

-L/usr/lib64 -lgsl -lgslcblas -lm

Additional info:

Comment 1 Florian La Roche 2005-02-13 14:50:02 UTC
Maybe removing this from the spec file and using the %_libdir (??)
macro is best?


Comment 2 Jay Turner 2005-04-14 15:12:52 UTC
Fixed with gsl-1.5-2.rhel4.  Moving to PROD_READY.

Comment 3 Tim Powers 2005-06-09 12:18:13 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2005-172.html