[puppy-devel] Re: library usage and known missing library bugs

On Wed, 08 Feb 2006 08:27:40 -0800
"Jonathan Marsden" <jmarsden@xxxxxxxxxxx> wrote:
> > Any known bugs other than the OpenSSL headers & libexif?
> I responded with one I knew of, curl.  

Well, this is a different problem, right?
The problem with OpenSSL & libexif are around header versions not matching the 
installed library versions.
Curl has a library missing - this is a straight Puppy, not a usr_devx.sfs 
issue, right?

> > If anyone has a list of dependencies for each of the libs, that would
> > be great...if not, we should probably start 1...
> Can't we automatically produce such a list?  Basically run ldd over
> every dynamically linked executable in the distribution, recording the
> results, and then sorting by library?  It doesn't sound like something
> that should be created by hand, to me.

Great, much better :)
I'll see what I can achieve with this...

> Modifying my one-liner for this a little leads to 
-CUT-
> and so (b) a list of binaries that have missing libs:
>   for i in `find / -type f -perm +1 |grep -v ^/\.usr \
>     |xargs file |grep executable |grep Intel |grep dynamic \
>     |cut -d : -f1 ` ; do echo $i: `ldd $i |grep "not found"` ; \
>     done |grep "not found"
> displays a list of programs and the libs they are missing.  

Cool :)
I can use this to check my remaster & see if I've broken any more apps than 
were already broken ;)

> On this system (Puppy 1.0.7, on hard disk) it outputs:
-CUT-
> So I suppose we can add each of those to the list of "known bugs".

I've posted this to the Bugs forum, which is the closest thing we have to an 
IssueTracker which is used by Barry, who's the man who can actually do 
something about it...

I see it more as a list of broken apps which can be removed than of libs that 
need adding ;)
- although they all seem to be stripped out of my remaster anyway...oh well...

F

Other related posts: