From: Rafael L. <lab...@ps...> - 2003-10-07 14:35:29
|
* João Cardoso <jc...@fe...> [2003-10-06 16:41]: > Under a alphaev6-dec-osf4.0f, with gcc-3.0.3, > > With a plain ./configure --prefix=... > > checking for sin in -lm... yes > checking for a Python interpreter with version >= 1.5... configure: > error: no suitable Python interpreter found > > and configure stops. Shouldn't it continue, with python disabled? Yes, this would be the preferable situation, but it is not completely under our control, because the python version checks are done in macro AM_PATH_PYTHON, included in aclocal.m4 by the aclocal command. We are not allowed to change this file, since it is automatically generated. There is a workaround, though, by redefining temporarily the AC_MSG_ERROR macro around the call to AM_PATH_PYTHON. The m4 trick is like this: pushdef([AC_MSG_ERROR],defn([AC_MSG_WARN])) AM_PATH_PYTHON(1.5) popdef([AC_MSG_ERROR]) Then, instead of stopping when python is not available, configure continues but barks like this: [...] checking for sin in -lm... yes checking for a Python interpreter with version >= 1.5... configure: WARNING: no suitable Python interpreter found : checking for :... no checking for : version... ./configure: line 1: -c: command not found checking for : platform... ./configure: line 1: -c: command not found checking for : script directory... ${prefix}/lib/python/site-packages checking for : extension module directory... ${exec_prefix}/lib/python/site-packages "Uhhh." warning: Java Native Interface include file not found checking for main in -lgd... yes [...] What do you think? Should I commit this change? -- Rafael |