On 12/31/2013 12:37 AM, Bruce Dubbs wrote:
> Frans de Boer wrote:
>> Dear reader,
>>
>> While building things again, I now start to wonder why LFS let almost
>> every package installs a static library? Where are the static libraries
>> used?
>>
>> After all, the down side of static libraries is tha
(Answering to both William and Bruce)
Okay, so that's how you solve that!
--
Svi moji e-mailovi su kriptografski potpisani. Proverite ih.
All of my e-mails are cryptographically signed. Verify them.
--
You don't need an AI for a robot uprising.
Humans will do just fine.
signature.asc
Descripti
On Dec 31, 2013, at 8:38 AM, Aleksandar Kuktin wrote:
> There is actually a problem with libtool and just rm-ing a static
> library. I don't know the specifics of it, but subsequent build
> attempts of other packages needing the affected libraries may fail.
You can safely remove all *.la as well
Aleksandar Kuktin wrote:
>> On Tue, 31 Dec 2013 07:49:11 -0600
>> William Harrington wrote:
>
>> After your whole build is done, you can use rm to remove them.
>
> There is actually a problem with libtool and just rm-ing a static
> library. I don't know the specifics of it, but subsequent build
>
>On Tue, 31 Dec 2013 07:49:11 -0600
>William Harrington wrote:
> After your whole build is done, you can use rm to remove them.
There is actually a problem with libtool and just rm-ing a static
library. I don't know the specifics of it, but subsequent build
attempts of other packages needing the
On Dec 31, 2013, at 3:07 AM, Simon Geard wrote:
> I quickly realised that I was just wasting my
> time for no real benefit.
>
> Simon.
After your whole build is done, you can use rm to remove them.
But if you are removing static libraries during your build,
just be sure to keep your glibc *_pic
On Mon, 2013-12-30 at 23:29 +0100, Frans de Boer wrote:
> Dear reader,
>
> While building things again, I now start to wonder why LFS let almost
> every package installs a static library? Where are the static libraries
> used?
Short version, because it's easier to let them install a static libr
On Tue, 2013-12-31 at 01:41 +, Ken Moffat wrote:
> I think many LFS/BLFS builders don't care about these sort of
> problems. It was a tedious buisness to disable static libs in BLFS.
Yeah... I pass --disable-static to all BLFS packages as a matter of
scripting, even if not all respect it. Bu
On Mon, Dec 30, 2013 at 11:29:34PM +0100, Frans de Boer wrote:
> Dear reader,
>
> While building things again, I now start to wonder why LFS let almost
> every package installs a static library? Where are the static libraries
> used?
>
They can sometimes be used if you mis-install one of the p
Frans de Boer wrote:
> Dear reader,
>
> While building things again, I now start to wonder why LFS let almost
> every package installs a static library? Where are the static libraries
> used?
>
> After all, the down side of static libraries is that once linked into a
> module/program, any upgrade i
Dear reader,
While building things again, I now start to wonder why LFS let almost
every package installs a static library? Where are the static libraries
used?
After all, the down side of static libraries is that once linked into a
module/program, any upgrade is not incorporated. Potentially
11 matches
Mail list logo
