One final question, which is not specific to boost::python but
general question on building Python modules.   What my Solaris
administrators have done is to configure Python with 

>   ./configure
 --prefix=/afs/.slac.stanford.edu/package/python/common/2.0
 --exec-prefix=/afs/.slac.stanford.edu/package/python/sun4x_55/2.0

They also did a build fron Linux with the appropriate `exec-prefix'.
What apparently this has done is to put all but one of the Python
include files in the directory `common/2.0/include'.  But Python.h
includes `config.h' or `pyconfig.h' (depending on the version) which
gets installed in `sun4x_55/2.0/include'.  This is appropriate since
this file is machine/OS dependent.

   Now the problem is that boost::python, and other packages, gives you
one variable, like PYTHON_INCLUDES,  for its build.   When it is set to find
`Python.h' it will not find `pyconfig.h'.   

   What is the best way to handle this situation?   Is it a bug in
Python's configure script?   Bug in boost::python and others?   Or am
I missing something obvious?

_______________________________________________
C++-sig mailing list
C++-sig@[...].org
http://mail.python.org/mailman/listinfo/c++-sig