A fix for the problem mentioned below was put into CVS a little while
ago. However there is a new problem with detection of python.h due to
versioned subdirectories in /usr/include. Toby and I are working on it
at the moment.
Francesco Grandis wrote:
> Geoffrey Biggs <g.biggs <at> auckland.ac.nz> writes:
>>If a debug python interpreter is used then the Python bindings will not
>>be selected for building by configure. This is because the configure
>>test checks if the output of 'python -c "import distutils"' is an empty
>>string, but with a debug interpreter it isn't. This means that the line
>>ac_distutils_result=`python -c "import distutils" 2>&1`
>>if test -z "$ac_distutils_result"; then
>>fails, even if the actual command works fine:
>>~/src/player $ python -c "import distutils" 2>&1
>>I've submitted a bug about this:
> Following the comment on the bug tracker i updated my player to HEAD, but i
> still get the same error. I've already verified that
> python -c "import distutils"
> gives no error message in the usual interpreter, so i assume PYTHONPATH is
> set up correctly (/usr/lib/python2.4/site-packages), but still no luck with
> configure. I modified configure to force building distutils since i know
> they're present, but it's not a long-term solution. What could i be missing?
> On a second-mind thought, i verified that actually the PYTHONPATH variable
> has no influence on "import distutils". Anyway
> python -v -c "import distutils"
> give me:
> import distutils # directory /usr/lib/python2.4/distutils
> # /usr/lib/python2.4/distutils/__init__.pyc matches
> import distutils # precompiled from
Robotics research group, University of Auckland