[Parted-maintainers] Bug#697779: pyparted: Use 'python-config --includes' to correctly detect multiarch include paths

[Colin Watson]

On Wed, Jan 09, 2013 at 09:12:57AM -0700, Tim Gardner wrote:
> diff -Nru pyparted-3.6/debian/rules pyparted-3.6/debian/rules
> --- pyparted-3.6/debian/rules	2013-01-07 04:26:13.000000000 -0700
> +++ pyparted-3.6/debian/rules	2013-01-09 08:58:36.000000000 -0700
> @@ -20,7 +20,7 @@
>  override_dh_auto_build:  
>  	for pyvers in ${PYTHONS}; do \
>  		(cd build/py$$pyvers/; $(MAKE) PYTHON=python$$pyvers); \
> -		(cd build/py$$pyvers-dbg/; $(MAKE) PYTHON=python$$pyvers-dbg PYTHON_INCLUDES=`python$$pyvers-dbg-config --include`); \
> +		(cd build/py$$pyvers-dbg/; $(MAKE) PYTHON=python$$pyvers-dbg PYTHON_INCLUDES=`python-config --includes`); \
>  	done
>  
>  override_dh_auto_install:

As discussed on IRC, this is wrong.  python$$pyvers-dbg-config is the
correct script to use, not python-config, and it exists so this isn't
the problem.  I believe the problem is that m4/python.m4 requires PYTHON
to be a full path in order to do header detection properly, and so the
PYTHON variable passed to configure needs to be a full path.

-- 
Colin Watson                                       [cjwatson at debian.org]