On Tue, Oct 30, 2018 at 09:06:47PM +0000, Hans Malissa wrote:
>
> ĸen
>
> Thanks for the explanation. So is it generally a good practice to search for
> any *.a and *.la files that might have gotten installed while building &
> installing a package, and to delete them manually?
>
> Hans
Personally, I'm always reluctant to *delete* installed files after
the expense of installing them. I do that to static libs for a
_few_ BLFS and Beyond-BLFS packages, and after a lot of testing I
keep some of the toolchain libs as '.a' to allow tests (and probably
also to support configure fragments).
In general, I rename ,a and .la files by adding '.hidden' on the end
of the name.
Looking at my scripts, I see that I'm not doing that for libtool
archives from ImageMagick : I'm fairly sure that BLFS's current
configuration means those too are not now required - but I haven't
tested that. My script also notes that gphoto2 (can't remember when
I tried that, it's certainly not part of my normal build) required
the libtool archives. People have also had problems upgrading BLFS
package versions if they removed the .la files after building a
series of packages (my scripts have a lot of overhead and I do all
the renaming as soon as each package is installed).
ĸen
--
Is it about a bicycle ?
--
http://lists.linuxfromscratch.org/listinfo/lfs-chat
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
