On Mon, Jun 22, 2009 at 6:11 PM, DJ Lucas wrote:
> And I thought that I had been complaining on this long enough so that we
> would never violate the FHS again. ;-) Even as rare as a remote /usr
> mount is now days, libz really must be moved to /lib if anything in /bin
> or /sbin links against it
DJ Lucas wrote:
> Tobias Gasser wrote:
>> Gilles Espinasse schrieb:
>>
i don't link anything static. i move all .a files out of the library
path if there is a corresponding .so available.
excptions are the modutils package (which require libc and libz to be
linked static
Tobias Gasser wrote:
> Gilles Espinasse schrieb:
>
>>> i don't link anything static. i move all .a files out of the library
>>> path if there is a corresponding .so available.
>>>
>>> excptions are the modutils package (which require libc and libz to be
>>> linked static), and sysvinit (libcrypt
Gilles Espinasse schrieb:
>> i don't link anything static. i move all .a files out of the library
>> path if there is a corresponding .so available.
>>
>> excptions are the modutils package (which require libc and libz to be
>> linked static), and sysvinit (libcrypt) where i copy the static
>> libr
Selon Tobias Gasser :
> Bruce Dubbs schrieb:
> > Static linking for this is OK with me, but do we know all the packages that
> use
> > libuuid?
>
>
> i don't link anything static. i move all .a files out of the library
> path if there is a corresponding .so available.
>
> excptions are the modutil
Bruce Dubbs schrieb:
> Static linking for this is OK with me, but do we know all the packages that
> use
> libuuid?
i don't link anything static. i move all .a files out of the library
path if there is a corresponding .so available.
excptions are the modutils package (which require libc and li
