ldconfig? /usr/lib64 LD_LIBRARY_PATH

[Jean-Marc Pigeon <jmp@safe.ca>]

[-- Attachment #1: Type: text/plain, Size: 2679 bytes --]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello,

I now have a set of packages (76,... gcc, make, git, etc.)
which are compiled with musl, all the way up to the
linux kernel.
With those packages I have reached my immediate goal of
having a self-sufficient distribution (the generated distribution can
recreate itself, see www.osukiss.org if you want
to know more).

I started from a simple glibc set of packages
and I converted them to musl while trying to have the
"minimal delta", keeping some package (ex: gettext,
ncurses?, ...) will be decided later on.
In the end I want a "clean, lean, strictly within
standards" set of packages, musl being a good example.

For now I have a problem with libraries, and I would
like to have a better understanding about what is suggested
about library PATH.

All packages 'configure' set their library to be in /usr/lib64,
many libraries (acl,...) without RPATH wants/needs them
within /lib. I bypassed the problem by sym-linking
needed libraries between /lib and /usr/lib64.

I rather prefer to have libraries only within /usr/lib64
(or /usr/lib for i686), sure enough I can hardcode
LD_LIBRARY_PATH within profile but I do not like this
solution.

ldconfig seems not available with musl.

Is there a easy/standard way in musl to set
the libraries in designated area?

Thanks for your help.

- -- 

A bientôt
===========================================================
Jean-Marc Pigeon                        E-Mail: jmp@safe.ca
SAFE Inc.                             Phone: (514) 493-4280
  Clement, 'a kiss solution' to get rid of SPAM (at last)
     Clement' Home base <"http://www.clement.safe.ca">
===========================================================
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.14 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBAgAGBQJVN+VNAAoJEAtgwJ4bBQU5bt0P+wQEFBGA3YAMxXBqnZUS1VsM
1blw917i0j2YYrQHVysFNjb/spNNatU52XOBFclQaGU/YCtlR0DhJCJeVxrPS/u6
Ufihn1RD6HKNFm1d8XwJLKknzIFljb8NXXZlvMgj1CyjEY8yWbYEMRDBkVJ6KtlD
u4LmwGD/Czn/uSuyPTYpMCu3i5LCc6KaUYZ4+x6MZ8oY/te0hiE0TsvjQ/U4X746
r3bzm6qwJBZ4CH4tr6KmHzxfhopxjFc+qEy3e2iMx5aoaNYmSxkOsDvUcYVLkpiM
DKLr3rgnfnkntcYop8yrkR7O7HPp1P2Re4MQ4HM7RELHG+NmCaHqruMv3/1tSHqp
a4AQmqypj0pXBNONglH5t+IpylElB4FdD6biInBIYddG308ZFT+M2HXTqE04rHlk
Wn0lGFFJ4UHEvNrvVaZ80Rtd3y1obIlgQUq39ZsuzLFglyGo+HBIJ5cL81wX24NV
XsLTbgQa8htPoS5VAgtgWdS6WFlcE3noIOoKXafXb+Q8xj1onEfe6A1APn407mJJ
qrDGkmye1XB9pv8TGL9cKwYcp2W8sZCY/+d8yYx1kDo8mIUpzPxfTlMGlZuWdqO0
c362fczGW6Lnu48C36ZNAZP27VK6kosUPsvD5/E73Z/2tLsYCJNIf9o/n4feAE3D
zzoAKxyMyp1GN3GV5HDv
=wD58
-----END PGP SIGNATURE-----


[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4242 bytes --]