Next: , Previous: , Up: Problems with configure   [Contents][Index]


8.1.6 Problems with ‘C compiler used for Python extension modules

The following message from configure is not uncommon:

 * Not building the Python interface to the coNCePTuaL run-time
   library because the C compiler used for Python extension modules
   (gcc -pthread) can't link against the output of gcc

Without the Python interface, none of the Python-based backends can be built, either:

 * Not installing the coNCePTuaL interpreter because it depends upon
   the Python interface to the coNCePTuaL run-time library
 * Not installing the statistics backend because it depends upon the
   coNCePTuaL interpreter
 * Not installing the PICL backend because it depends upon the
   coNCePTuaL interpreter
 * Not installing the Paraver backend because it depends upon the
   coNCePTuaL interpreter
 * Not installing the LaTeX visualization backend because it depends
   upon the coNCePTuaL interpreter

Note that coNCePTuaL is still quite usable without the Python-based backends; the C+ MPI backend (see The c_mpi backend), for example, does not rely on Python.

A typical cause of the ‘can't link’ message is that the configure script is unable to locate the Python development files that are needed to build a Python module. Most Python installations exclude the development files by default, requiring that they be installed separately. In some Linux distributions these files are provided by a package with a name like python-dev. A key file to look for is Python.h. If ./configure cannot find Python.h, the ‘can't link’ message will almost certainly appear.


Next: , Previous: , Up: Problems with configure   [Contents][Index]

Scott Pakin, pakin@lanl.gov