Hide Forgot
Description of problem: If your application uses libtool, you can't successfully link with libxmlsec1, libxmlsec1-gnutls, or libxmlsec1-openssl. Version-Release number of selected component (if applicable): xmlsec1-devel-1.2.7-4 xmlsec1-gnutls-devel-1.2.7-4 xmlsec1-openssl-devel-1.2.7-4 libxml2-devel-2.6.19-1 How reproducible: Always Steps to Reproduce: 1. cat > foo.c << EOF int main(int argc, char **argv) { return 0; } EOF 2. libtool --mode=compile gcc -c -o foo.lo foo.c 3. libtool --mode=link gcc -o foo foo.lo -lxmlsec1 Actual results: libtool: link: cannot find the library `/usr/lib/libxml2.la' Expected results: No output, successful link. Additional info: This should fix itself if we just bump the release number and recompile the package.
php cannot compile without /usr/lib/libxml2.la because it greps it when building modules, etc. This cannot be seen without a completely distilled environment. My recommendation is to just package /usr/lib/libxml2.la with libxml2-devel. This in %files already does this: %{_libdir}/*a Just need to take away the "rm -f" completely.
w.r.t. #2. No this is a policy decision, we won't packages .la anymore. Daniel
Nalin's suggestion is the right one. Now that /usr/lib/libxml2.la is gone, all packages that currently contain libtool archives themselves that include references to (the now-missing) libxml2.la need to be rebuilt (and potentially remove/omit their .la files as well).
If it wasn't clear from my comment #3, it appears that xmlsec1 simply needs to be rebuilt.
Though this bug is marked against -devel, it appears that it should be against fc4, since xmlsec1-1.2.7-4 is the version from fc4.
I just confirmed a rebuild is successful and fixes the problem (as originally reported). Future xmlsec1 builds (probably targeted at -devel/fc5) probably ought to not include libtool archives (/usr/lib/lib*.la) or static libs (/usr/lib/lib*.a) either, but that's a separate issue.
FYI, see bug #171410: "remove *.la/*.a files"
Okay the extra .la should have been removed some time ago, but I forgot. It should be fixed in rawhide, with the upcoming 1.2.9-7, Daniel