mjpegtools build error, missing libs which aren't missing

vdemuth · 03-14-2010, 04:51 AM

Hi all,

trying to build mjpegtools 1.90 using the slackbuild script but getting this build error

Code:

gcc: /usr/lib64/libgobject-2.0.so: No such file or directory
gcc: /usr/lib64/libgmodule-2.0.so: No such file or directory
gcc: /usr/lib64/libglib-2.0.so: No such file or directory

Looks then as if these libs aren't available. However, a locate finds them in /usr/lib and /usr/lib64 where they are expected to be.

Anyone any ideas, or alternatively a link to an alrady compiled pkg for Slackware64

TIA

datopdog · 03-14-2010, 05:00 AM

locate may provide you with incorrect information as it relies on being updated, check for the files using find or by just doing ls /usr/lib64

vdemuth · 03-14-2010, 05:57 AM

Tried that and they show in the directory /usr/lib64 absolutely fine. But strangely enough ldconfig shows this error:-

Code:

ldconfig: Cannot stat /usr/lib64/libslang.so: No such file or directory
ldconfig: Cannot stat /usr/lib64/libgthread-2.0.so: No such file or directory
ldconfig: Cannot stat /usr/lib64/libglib-2.0.so: No such file or directory
ldconfig: Cannot stat /usr/lib64/libgmodule-2.0.so: No such file or directory
ldconfig: Cannot stat /usr/lib64/libcurl.so: No such file or directory
ldconfig: Cannot stat /usr/lib64/libmp.so: No such file or directory
ldconfig: Cannot stat /usr/lib64/libgobject-2.0.so: No such file or directory
ldconfig: Cannot stat /usr/lib64/libtiff.so: No such file or directory

Any more ideas?

vdemuth · 03-16-2010, 02:56 AM

anyone?

GrapefruiTgirl · 03-16-2010, 03:12 AM

Right, so post #1 and post #3 are conflicting. Either the missing libs are on the system, or they are not.

The ldconfig output showing all those "cannot stat.." messages, suggests that the libraries are not present on the machine, but symlinks to them are still present (i.e. symlinks pointing at non-existent stuff).

Also, the libraries should NOT be found BOTH in /usr/lib AND in /usr/lib64 -- this doesn't make sense (forgive me if it's a multi-lib system and it actually DOES make sense -- I've not used multi-lib, so I could be wrong there, I don't know.)

Is this happening on your Slackware --current system? Is it updated, and not missing any packages?

I suggest the following commands:

Code:

grep usr/lib64/libgmodule-2.0.so /var/log/packages/*

repeat that command, replacing the bold part with each of the items shown in post #1 and post #3 -- and leave off the leading slash! It looks like you have missing, corrupted, or overlapped packages installed.

You might find my lib/dependency checking script handy; you can get it here: http://www.linuxquestions.org/questi...encies-794133/

Cheers!
Sasha

vdemuth · 03-16-2010, 12:52 PM

Hi Sasha,

This is indeed a multilib system running current so that may be part of the problem. However, following your suggestion I get this result:

Code:

grep usr/lib64/libgmodule-2.0.so /var/log/packages/*
/var/log/packages/aaa_elflibs-13.013-x86_64-4:usr/lib64/libgmodule-2.0.so.0.2200.4
/var/log/packages/glib2-2.22.4-x86_64-1:usr/lib64/libgmodule-2.0.so.0.2200.4
grep usr/lib64/libgobject-2.0.so /var/log/packages/*
/var/log/packages/aaa_elflibs-13.013-x86_64-4:usr/lib64/libgobject-2.0.so.0.2200.4
/var/log/packages/glib2-2.22.4-x86_64-1:usr/lib64/libgobject-2.0.so.0.2200.4
/var/log/packages/glib2-2.22.4-x86_64-1:usr/share/gdb/auto-load/usr/lib64/libgobject-2.0.so.0.2200.4-gdb.py
grep usr/lib64/libglib-2.0.so /var/log/packages/*
/var/log/packages/aaa_elflibs-13.013-x86_64-4:usr/lib64/libglib-2.0.so.0.2200.4
/var/log/packages/glib2-2.22.4-x86_64-1:usr/lib64/libglib-2.0.so.0.2200.4
/var/log/packages/glib2-2.22.4-x86_64-1:usr/share/gdb/auto-load/usr/lib64/libglib-2.0.so.0.2200.4-gdb.py

As you can see, the 'missing' libs are included in aaa_elflibs, albeit with extended release info. I have checked that the symlinks are named correctly and point to these libs. I can't help thinkiong that somewhere along the line in updating to current I have somehow borked my box.

I have tried your script BTW and it gives me loads of orphaned files and missing binaries, so still deciding what to do about that. Just for info though, as well as multlib, I am running AlienBob's KDE4.4.1 packages and kde3 compat packages both 32 and 64bit. Perhaps time to remove the kde3 stuff!

GrapefruiTgirl · 03-16-2010, 12:57 PM

Well, first thing I would do is try to reinstall those packages which contain the pieces that your system seems to be missing; i.e. make sure that all packages that are SUPPOSED to be installed, are actually installed fully/correctly, and that remnants of OLD packages are not lying around..

As for multilib and the KDE stuff, I'm using neither so unfortunately I can't accurately comment on what's right or wrong on your system from that perspective.

Sasha