ldconfig? /usr/lib64 LD_LIBRARY_PATH

ldconfig? /usr/lib64 LD_LIBRARY_PATH

[Jean-Marc Pigeon]

[-- 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 --]

Re: ldconfig? /usr/lib64 LD_LIBRARY_PATH

[Rich Felker]

On Wed, Apr 22, 2015 at 02:15:41PM -0400, Jean-Marc Pigeon wrote:
> -----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?

Just place the paths you want searched in a file named
/etc/ld-musl-x86_64.path (or replace x86_64 with your arch, the same
as the name in /lib/ld-musl-*.so.1), separated by newlines or colons.
If this file exists it will replace (not add to) the default search
path, so you need to include all dirs you want searched.

Note that ld-musl-*.so.1 itself needs to be in /lib.

Rich

Re: ldconfig? /usr/lib64 LD_LIBRARY_PATH

[Jean-Marc Pigeon]

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

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

On 04/22/2015 02:37 PM, Rich Felker wrote:
> On Wed, Apr 22, 2015 at 02:15:41PM -0400, Jean-Marc Pigeon wrote:
>> -----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?
> 
> Just place the paths you want searched in a file named 
> /etc/ld-musl-x86_64.path (or replace x86_64 with your arch, the
> same as the name in /lib/ld-musl-*.so.1), separated by newlines or
> colons. If this file exists it will replace (not add to) the
> default search path, so you need to include all dirs you want
> searched.
> 
> Note that ld-musl-*.so.1 itself needs to be in /lib.
> 
> Rich
> 
Many many Thanks Rich...

Question: where is doc about this? (I should had find it myself).


- -- 

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/GQAAoJEAtgwJ4bBQU5BpgQAJ9FCAVkM3AkVRensVisehkP
hHHOrVvEtYh3lidkbGIhsTC0uIw6jWx1L146E+YpR0xCJA09kzXWbfGjB9N59s1m
oB3wM5JB+PJJIMA4ecvGmdgM/rcAdW/ZwjhlvhNk7Md1hWU7isiIDgEI/NoRVWeC
w6A6u4QUhFmNIzZS+/mtIdOpURpbPUBq3RadqGmaaQX2K47noKBeSlKcqEL99Dbj
s9t9JnMSqZbq+klJ49Cm7LqSWt1qUKfVSXnH0e7x6lVdImt6maJuAOMHIzut/9mm
Qif8xycu01J6UYcgkxIw2s2WS6jPAOepcRwGWnDL2LPFTtMHO/iI5EEIJWJ5eLXv
sKyd/OPlzpQDQRG7Qa0J5xo40syVUx0LJGNvBpui476b612zhcDZXLwqgTuWQOVN
CqiE36fZSI8oDD9CuuXn8KxXZbw48CZ5fGQXTMlaw0v4dsFyOfp8/0OL57D0GtF1
0/5EQX8NBRhcZ+NkslKJT4WGdbdG7F5G93p7A6dT7ICqnv7dsIEj3GZyjoUJFnHw
Tzl74krClKEriOA+tDaoJy6dAQ7uwPAWrJqMEq4EbCcO7NUy0mSQSeVnO0Pw+dTp
cRonFj4mnB5vafbYEIk5Gi0EflaX8W8T2JrJqloqAq5U1GnpanYBwtklNSI4w6xE
jHkeCrOp/ktUl1FnrXO3
=6Qd0
-----END PGP SIGNATURE-----


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

Re: ldconfig? /usr/lib64 LD_LIBRARY_PATH

[Rich Felker]

On Wed, Apr 22, 2015 at 03:08:01PM -0400, Jean-Marc Pigeon wrote:
> >> Is there a easy/standard way in musl to set the libraries in
> >> designated area?
> > 
> > Just place the paths you want searched in a file named 
> > /etc/ld-musl-x86_64.path (or replace x86_64 with your arch, the
> > same as the name in /lib/ld-musl-*.so.1), separated by newlines or
> > colons. If this file exists it will replace (not add to) the
> > default search path, so you need to include all dirs you want
> > searched.
> > 
> > Note that ld-musl-*.so.1 itself needs to be in /lib.
> > 
> Many many Thanks Rich...
> 
> Question: where is doc about this? (I should had find it myself).

It's in the documentation on the website at:

http://www.musl-libc.org/manual.html

Note that it's not up-to-date with current musl and not complete, but
it covers most of the important things to know from a non-developer
(i.e. just end user or deployment/integration) standpoint.

Rich