GNOME Bugzilla – Bug 546563
Build breaks because of libpython check
Last modified: 2008-08-14 13:05:05 UTC
configure.in attempts to check if libpython is linkable (why does it have to do that?) by manually invoking libtool. Currently libtool requires you to pass --tag=CC to choose the configuration and failing to pass it causes an error. Furthermore there is no ../libtool executable until the configure script finishes so python support is never enabled. I propose removing the check altogether as it seems to be an overkill (we don't check linkability of all the other libraries, right?).
Created attachment 115959 [details] [review] Disable the libpython check
Works fine here...
Bastien: 1. First remove the >/dev/null redirection in that python test (in configure.in) and regenerate the configure script. 2. Then delete the "libtool" file (as it's not part of distribution, at least not part of the tarballs). It is marked as being generated by configure which is true. 3. Next run configure to see that it fails on missing "../libtool" executable. 4. Also notice that there is a "libtool" file (it's generated at the very end od the configure script, as noted in point 2. above) 5. Re-run configure and now it succeeds as the "libtool" file from the previous run is still around I imagine steps 2-4 could be reproducible by "make distclean; make distcheck". Still the test is pointless and even when it works libtool complains about a missing --tag=CC param (using libtool 2.2.4 here) which is just hidden by redirecting the output to /dev/null.
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 532591 ***