[Devel] [ openser-Bugs-1476285 ] installs to wrong libdir

SourceForge.net noreply at sourceforge.net
Tue May 2 17:10:14 CEST 2006

Bugs item #1476285, was opened at 2006-04-25 13:17
Message generated for change (Comment added) made by squinky86
You can respond by visiting: 

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: packaging
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Jon Hood (squinky86)
Assigned to: Nobody/Anonymous (nobody)
Summary: installs to wrong libdir

Initial Comment:
I'm on a 64 bit system. There are sed commands that
point to /usr/lib. My lib directory is /usr/lib64. One
way to fix this would be a ./configure script that
generates the makefile for you.

Also, when I run the following:
make DESTDIR=/usr/local/openserinstalltest install
it will attempt to install libraries in /lib. I have no
/lib. The correct place for the libraries it installs,
however, is /usr/lib(64). This should be set by the
LIBDIR variable.


>Comment By: Jon Hood (squinky86)
Date: 2006-05-02 10:10

Logged In: YES 

Yes, /usr/lib64 is the default for _most_ 64-bit
architectures; however, to be safe, the preferred method is
to define a libdir variable that the installation obeys.
There are a number of packages that don't obey the libdir
settings and just install to /usr/lib. For people on
multi-lib systems (mixed 32 and 64 bit libraries), this
poses a problem. There's no way to differentiate between the
32 and 64 bit libraries when they're in the same directory.
Users that don't care what libraries they're using often
symlink /usr/lib to /usr/lib64.
If you need more explanation, feel free to email me directly
or IM me: jon at asteriasgi.com (MSN messenger).


Comment By: Daniel-Constantin Mierla (miconda)
Date: 2006-05-02 04:32

Logged In: YES 

Is /usr/lib64 the default for 64b architectures? I try to
figure out if should be used for all 64b archs or just for some.


You can respond by visiting: 

More information about the Devel mailing list