Bug 127691

Summary: boost libraries are in /usr/lib instead of /usr/lib64
Product: [Fedora] Fedora Reporter: Dag Wieers <dag>
Component: boostAssignee: Benjamin Kosnik <bkoz>
Status: CLOSED NEXTRELEASE QA Contact:
Severity: low Docs Contact:
Priority: medium    
Version: 2CC: mnewsome
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: 2005-03-16 23:14:31 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 Dag Wieers 2004-07-12 16:50:27 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6)
Gecko/20040510 Galeon/1.3.16

Description of problem:
The boost libraries on x86_64 are in /usr/lib instead of /usr/lib64.
Although the binaries actually are 64bit.

    [root@fc2a /]# rpm -qf /usr/lib/libboost_date_time.so.1.31.0
    boost-1.31.0-7

    [root@fc2a /]# file /usr/lib/libboost_date_time.so.1.31.0
    /usr/lib/libboost_date_time.so.1.31.0: ELF 64-bit LSB shared
object, AMD x86-64, version 1 (SYSV), stripped



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


How reproducible:
Always

Steps to Reproduce:
1. - 
2.
3.
    

Additional info:

Comment 1 Benjamin Kosnik 2004-11-29 18:50:57 UTC
This should be fixed with the -9 version of the package, in FC3. The
boost rpm now uses _libdir, so this should be correct.

Can you please confirm?

best,
benjamin

Comment 2 Benjamin Kosnik 2004-11-30 17:35:05 UTC
Dag, I've updated boost to the 1.32.0 release. Can you confirm that
these packages (should be pushed out soon)

http://people.redhat.com/bkoz/boost-1.32.0/

Have fixed this issue?

thanks,
benjamin

Comment 3 Dag Wieers 2004-11-30 23:28:01 UTC
I made a quick rebuild on x86_64 and it seems ok.

[root@lisse src]# rpm -qpl /tmp/x86_64/boost-1.32.0-1.x86_64.rpm
/usr/lib64/libboost_date_time.so.1.32.0
/usr/lib64/libboost_filesystem.so.1.32.0
/usr/lib64/libboost_prg_exec_monitor.so.1.32.0
/usr/lib64/libboost_program_options.so.1.32.0
/usr/lib64/libboost_python.so.1.32.0
/usr/lib64/libboost_regex.so.1.32.0
/usr/lib64/libboost_signals.so.1.32.0
/usr/lib64/libboost_test_exec_monitor.so.1.32.0
/usr/lib64/libboost_thread.so.1.32.0
/usr/lib64/libboost_unit_test_framework.so.1.32.0

What worries me, is that the .so files are missing from the -devel
package. I'm not sure if this is the intended behaviour, rpm silently
ignores symlinks, so you may have forgotten them.

If they don't exist, either you'll have unowned files in _libdir, or
people cannot dynamically link to them at compile time.

Comment 4 Benjamin Kosnik 2004-12-02 17:10:11 UTC
Dag, I understand your .so comment now. Fixing...