From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-GB; rv:1.3) Gecko/20030314
Description of problem:
The .la file is produced by the buildprocess, but is not mentionedin the .spec
file, so is not included. This makes for problems linking it with applications
that need it.
Version-Release number of selected component (if applicable):
What apps actually *require* the libtool file?
Transcode needs the .la file.
FYI, the libogg package will not rebuild from .src.rpm any more as it builds and
installs libogg.la, but does not package it. It therefore fails when the
rpmbuild run checks for just this eventuality.
Actually, that rebuild issue has been fixed in the 9 version. I'm still not
entirely sure why transcode would need the .la file just to link to the library.
(IOW: excessive libtool use should be avoided. :) )
What does 'grep libogg.la /usr/lib/*.la' say?
Bearing in mind I have already corrected the spec file and rebuilt the libogg
package to include the file, so I could carry on with my work ....
$ grep libogg.la /usr/lib/*.la
/usr/lib/libogg.la:# libogg.la - a libtool library file
/usr/lib/libvorbisenc.la:dependency_libs=' -lm -L/usr/lib /usr/lib/libogg.la'
/usr/lib/libvorbisfile.la:dependency_libs=' -lm -L/usr/lib /usr/lib/libogg.la'
/usr/lib/libvorbis.la:dependency_libs=' -lm -L/usr/lib /usr/lib/libogg.la'
Woops, that appears to be a bug in the vorbis libs shipped with Red Hat Linux 8.
If you rebuild them against the libogg without the .la file, it should fix the
problem. This is fixed in Red Hat Linux 9.