[blfs-dev] Upcoming BLFS-7.5 release

Bruce Dubbs bruce.dubbs at gmail.com
Mon Mar 3 19:56:43 PST 2014


Ken Moffat wrote:
> On Mon, Mar 03, 2014 at 07:27:06PM -0600, Bruce Dubbs wrote:
>> Ken Moffat wrote:
>>>    I thought from an earlier reply that you considered these to be
>>> leftovers from when we had --libexecdir=/usr/lib in the commands for
>>> these packages.
>>
>> We may be discussing two different things.  Above I was addressing
>> general '<parameter>' vs '<option>' usage.
>>
>>> So, I was going to delete them.
>>
>> If we don't use --libexecdir in a package, then I don't think it needs
>> to be addressed at all other than the case when a new subdirectory is
>> created in /usr/libexecdir.  Then it's only documenting it fact that the
>> subdirectory is created.
>>
>   Too late, I've put it as an option for peopl using LFS before 7.5.

I saw that.  It's ok.  We may want to remove later though.

>   I've also reinstated libexecdir for sudo : everything in it is a
> library.

What is the matter with libraries in libexecdir?

I also have

/usr/libexec/gcc/x86_64-unknown-linux-gnu/4.8.2/liblto_plugin.so.0.0.0
/usr/libexec/gcc/x86_64-unknown-linux-gnu/4.8.2/liblto_plugin.so
/usr/libexec/gcc/x86_64-unknown-linux-gnu/4.8.2/liblto_plugin.so.0
/usr/libexec/coreutils/libstdbuf.so

Yes, I know the FHS says "Binaries run by other programs", but I suspect 
libraries are OK because the developers specifically do not want the 
linker to look for these libraries unless they explicitly specify it.

   -- Bruce



More information about the blfs-dev mailing list