Hi dd, On 03/27/2011 11:09 PM, dd wrote:
3) now there is an interesting error. the following line of the file "configure" (the one generated by "autogen")
if test "$ac_supports_python_ver != "True";
does't work because my system sets the variable ac_supports_python_ver to
$'True\r' (I don't know why...)
What is exactly the error that the configure scripts outputs when this happens?
and so a possible workaround is to substitute the line with
if test $ac_supports_python_ver != $'True\r';
It is best not do modifiy the configure script like this, since the behaviour can be unpredictable... You should modify configure.ac instead, and run autogen.sh.
4) now I have the following error.
configure: error: Could not link test program to Python. Maybe the main Python library has been installed in some non-standard library path. If so, pass it to configure, via the LDFLAGS environment variable. Example: ./configure LDFLAGS="-L/usr/non-standard-path/python/lib" ============================================================================ ERROR! You probably have to install the development version of the Python package for your distribution. The exact name of this package varies among them. ============================================================================
In order to understand why errors like this happen, you should look at the file config.log, which will say exactly why the test program did not link with the python library.
There is no file "conftest" in my folder... could it be a problem for the following instruction?
ac_compile='$CC -c $CFLAGS $CPPFLAGS conftest.$ac_ext >&5'
I have no idea how the variables in the configure script are defined, and what they mean... The configure script is not meant to be understood by humans; it is automatically generated from configure.ac. Usually it is possible to debug things by looking at config.log and modifying configure.ac and/or the m4 macros. Cheers, Tiago -- Tiago de Paula Peixoto <tiago@skewed.de>