libgpod 0.7.93 expects to see at least SWIG 1.3.24, but doesn't recognize that SWIG 2.0.0 > 1.3.24. Reproducible: Always Steps to Reproduce: 1. emerge --oneshot libgpod 2. Observe the following complaint during the configure phase: checking for SWIG version... 2.0.0 configure: WARNING: SWIG version >= 1.3.24 is required. You have 2.0.0. You should look at http://www.swig.org 3. After it's done installing, notice how /usr/lib/python2.6/site-packages/libgpod/ does not exist. Actual Results: No Python bindings were built. Expected Results: Python bindings should have been installed to /usr/lib/python2.6/site-packages/. This is a problem for any program that depends on the libgpod Python bindings, such as quodlibet. A workaround is to revert to the latest pre-2.0.0 SWIG (add the line ">=dev-lang/swig-2.0.0" to /etc/portage/package.mask, then emerge --update --deep --newuse world). Another is to alter libgpod-0.7.93's configure.ac and change the line SWIG_MIN_VERSION=1.3.24 to SWIG_MIN_VERSION=2.0.0, and rerun autoconf.
Created attachment 246791 [details, diff] Workaround for people with SWIG >= 2.0.0 We change SWIG_MIN_VERSION=2.0.0 in configure.ac. This does not solve the larger problem, namely Autoconf doesn't understand that 2.0.0 > 1.3.24.
Created attachment 246792 [details] An ebuild that applies -compile-with-swig-2.patch. I just mimicked the src_prepare() function from libgpod-0.7.2.ebuild. I don't really know what I'm doing, but it works.
checking for swig... /usr/bin/swig checking SWIG version... 2.0.1 checking for SWIG library... /usr/share/swig/2.0.1 [ .. ] Python bindings ..........: yes PyGObject support ........: yes [ .. ] Seems to be fixed in 0.8.0 without any changes
