Matthias Koenig wrote:
> Ludwig Nussel <[EMAIL PROTECTED]> writes:
> > A library required during system boot lives in /lib. Therefore one runs
> > configure --lib=/%_lib which means all files get installed into
> > /%_lib including the devel symlink *.so that point to the SONAME.
> > Some packages manually move that symlink to /usr. Does that have any
> > technical or cosmetic advantage?
>
> Yes, there has been a technical problem I've been running into when moving
> the libs of of libgpg-error and libgcrypt.
> The static libs are not allowed to reside in /%_lib they have to be in
> %_libdir (Also the libtools .la files). Since the linker seems to search
> first in %_libdir and then in /%lib, it does not find the .so link when
> linking and links against the static lib, which is not what we want.
> Richard Guenther and Michael Matz also acknowledged that the .so devel link
> has to reside in /usr/%_lib. Maybe they know more about this.
Ok. However, pkgconfig files typically specify -L${libdir} in their linker
flags which would result in -L/lib. So I guess it would actually make more
sense to run configure with %_libdir and then move non-devel files to /lib
instead of the other way around.
cu
Ludwig
--
(o_ Ludwig Nussel
//\ SUSE LINUX Products GmbH, Development
V_/_ http://www.suse.de/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
