Puppy Linux Discussion Forum

[musher0]

Hello all.

As the title says.

We have this huge LLVM library in the pup*.sfs of all Puppies. I read in the
wikipedia article about it that it is mostly good to help execution of programs
written in the Haskell and Java languages.

Maybe I understood this wrong, which is why I'm asking.

It's pushing 50 Mg's, so if we only need on certain occasions, why not make a
separate sfs of it, that people could load as needed? It would be a nice way to
trim down our future Pups.

TIA for any insights. BFN.

[s243a]

Here's some stuff from google:

[peebee]

[musher0]

@s243a: thanks for the additional info.

@peebee: also thanks for your reply.

However, on this trimmed xenialPup-706, I've transplanted the LLVM lib to the devx. I've
been running this Pup for 4 hours in a row without LLVM without any problems. Are
you sure this LLVM thing is not some kind of folklore or overstatement? You're an
experienced dev, of course, and I want to believe you, but what you say and my hands-
on experience do not jive.

I remember having had a similar conversation with former member ASRI. (It's on this
forum somewhere.) He ran his educational Pup without LLVM for a while and had no
problems.

How do we test this LLVM lib, to be sure it is needed by us simple mortals? Does it
leave a trace when it kicks in or after it has done so?

BFN.

[musher0]

Hello again, peebee.

This is the the size of the LLVM on my xenialPup-706:

[Sailor Enceladus]

I think if you build Slacko 14.1 it doesn't need llvm, but 14.2 uses it for some drivers. Maybe it's the same for Tahr vs. Xenial.

One way to see what may use it is to remove llvm with "Remove Builtin Packages" then run checkdeps / from terminal:
http://www.murga-linux.com/puppy/viewtopic.php?p=958690#958690

[musher0]

Many thanks, Sailor Enceladus.

@peebee: the github page for llvm-cut does not exist anymore.

Does anybody have a lead?

TIA

[peebee]

[musher0]

Hi peebee and all.

In other words, nothing at the moment. Thanks for being so frank!

In any case, I wasn't asking about our Puppy situation, but generally, if there exists
a trimmed down LLVM library.

I ran the test suggested by Sailor E. and got pretty much the same results.So the
utility of this LLVM lib is pretty much limited to Puppyists with fancy video cards.

So from now on, LLVM will be a separate sfs in my Pups: those who need it,
download it. Same as we've been doing for ages, with the devx. In so doing, we'll
be shaving 51 Mb's unpacked (or 29 Mb's squashed) off the iso for the majority
who don't need it.

Why make the majority pay -- download wise -- for the needs of the few.

Finally, this thread WAS useful. Thanks to all who contributed.

[rcrsn51]

At some point in the Puppy past, the decision was made to include accelerated video (mesa/dri). This would let users run things like Google Earth OOTB. This is how LLVM gets introduced.

So another approach is to remove all the mesa/dri stuff from the woof build.

Users can add it (and all the dependencies) as needed. This is how Stretch-Live handles it.

[dancytron]

[rcrsn51]

You would need to determine something first. Do sfs modules get loaded BEFORE X starts?

I used a similar trick in Devuan live where I put the firmware required by the radeon video driver in a squashfs module. It DID get loaded first and X started.

[dancytron]

[rcrsn51]

If not, an X restart might be required.

As a proof-of-concept, I made a squashfs module of libgl1-mesa-dri + mesa-utils. I dropped it into a Debian-live frugal install and it appears to be working.

[dancytron]