|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] [PATCH v2] autoconf: check for Python.h header and -lpython* lib
Roger Pau Monne writes ("[PATCH v2] autoconf: check for Python.h header and
-lpython* lib"):
> autoconf: check for Python.h header and -lpython* lib
Right, this is better.
> +ac_previous_cppflags=$CPPFLAGS
...
> +AC_CHECK_HEADER([Python.h], [],
> + [AC_MSG_ERROR([Unable to find Python development headers])],)
> +AC_CHECK_LIB($python_lib, PyArg_ParseTuple, [],
> + [AC_MSG_ERROR([Unable to find a suitable python development library])])
> +CPPFLAGS=$ac_previous_cppflags
> +LDLFAGS=$ac_previous_ldflags
But AFAICT we go to all this effort to find the right python flags and
then we throw them away. This is a bit odd. Shouldn't we be passing
this in some PYTHON_FOOFLAGS variables for the benefit of tools/python ?
Ian.
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel
|
![]() |
Lists.xenproject.org is hosted with RackSpace, monitoring our |