[CLAM] Re: Compile problem with id3
David García Garzón
dgarcia at iua.upf.edu
Thu Nov 2 03:27:55 PST 2006
I really don't know how to help. Did you compile the id3 libraries from scratch as you did with the fftw? If so, try to use already existing packages for SuSe or the ones for Fedora if SuSe doesn't have them. They should give you less problems, i hope.
On Thu, 02 Nov 2006 09:46:55 +0100
Gregor van den Boogaart <gregor.boogaart at informatik.uni-augsburg.de> wrote:
> Hi David,
> > Have you defined LD_LIBRARY_PATH environment
> > variable so that binaries can use libraries at /usr/local?
> Yes, LD_LIBRARY_PATH contains /usr/local/lib. But the problem is, that
> libid3.so is not found during linking.
> The *.so-files are in a path mentioned in /etc/ld.so.conf and all other
> files in /usr/local/lib are found during the run of ldconfig, e.g.
> libid3-3.8.so.3, but libid3.so is not found. I never had such a problem
> >> Nevertheless I have installed id3, CLAM is not able
> >> to link against it. I'm not shure, whether that's a problem of id3,
> >> ldconfig or CLAM itself. After installing id3, I've got in /usr/lib
> >> (from the distribution) and in /usr/local/lib (installed manually) the
> >> files:
> >> lrwxrwxrwx 1 root root 9 2006-10-31 12:01 libid3-3.8.so.3 -> libid3.so
> >> -rwxr-xr-x 1 root root 1723835 2006-10-31 11:43 libid3-3.8.so.3.0.0
> >> lrwxrwxrwx 1 root root 19 2006-10-31 12:01 libid3.so ->
> >> libid3-3.8.so.3.0.0
> >> lrwxrwxrwx 1 root root 18 2006-10-31 11:43 libid3tag.so ->
> >> libid3tag.so.0.3.0
> >> lrwxrwxrwx 1 root root 18 2006-10-31 11:43 libid3tag.so.0 ->
> >> libid3tag.so.0.3.0
> >> -rwxr-xr-x 1 root root 179176 2006-10-31 11:43 libid3tag.so.0.3.0
> >> That is libid3.so is only a link and not a shared object itself. Well,
> >> that shouldn't be a difference.
> > That's as it should be. Have you defined LD_LIBRARY_PATH environment variable so that binaries can use libraries at /usr/local?
> >> Nevertheless ldconfig does not recognize
> >> (?) it. From "ldconfig -p | grep id3" I get:
> >> libid3tag.so.0 (libc6) => /usr/local/lib/libid3tag.so.0
> >> libid3tag.so.0 (libc6) => /usr/lib/libid3tag.so.0
> >> libid3tag.so (libc6) => /usr/local/lib/libid3tag.so
> >> libid3tag.so (libc6) => /usr/lib/libid3tag.so
> >> libid3-3.8.so.3 (libc6) => /usr/local/lib/libid3-3.8.so.3
> >> libid3-3.8.so.3 (libc6) => /usr/lib/libid3-3.8.so.3
> >> I tried everything: replacing the link with a real file and many other
> >> things. ldconfig ignores libid3.so. Consequently the library is not
> >> found during "scons configure":
> >> ...
> I think, I've sent You for some reason the wrong error message from
> "scons configure". The current one regarding a problem with libid3.so is:
> Checking for mad_stream_init() in C library mad... yes
> Checking that libmad sample program compiles...ok
> Checking that libmad sample program links...ok
> Checking that libmad sample program runs... ok
> Checking for C++ header file id3.h... yes
> Checking for ID3_Tag myTag in C++ library id3... no
> Could not find id3lib binaries! Please check your id3lib installation
> Perhaps this helps? Again: the file libid3.so more precisely the link is
> present at the right place. But, in the ldconfig run, this file is
> either ignored or perhaps recognized as libid3-3.8.so.3 and consequently
> not found during linking. Still I'm not shure, wether that's a problem
> of id3lib, ldconfig or CLAM.
> Thanks for any help!
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
More information about the clam-users