Jim Gallacher wrote ..
> Indrek Järve wrote:
> > Jim Gallacher wrote:
> >
> >> And see if any tests fail. If they pass, send a +1 to the list, if they
> >> fail, send the details (the versions of OS, Python and Apache, the test
> >> output, and suggestions, if any).
> >>
> >> Thank you,
> >> Jim Gallacher
> >
> >
> > +1 on SuSE Linux 9.2 (i586)
> > +1 on SuSE Linux 9.2 (x86-64) once I edited the configure script and
> > replaced lib/ with lib64/ in PY_STD_LIB and PyLIBP
>
> I wonder how we might correctly determine the 'lib' part of the path.
> The relevant section of configure.in is:
>
> # find out compiled in install prefix
> AC_MSG_CHECKING(Python install prefix)
> PyEXEC_INSTALLDIR=`$PYTHON_BIN -c "import sys; print sys.exec_prefix"`
> AC_MSG_RESULT($PyEXEC_INSTALLDIR)
>
> # this is where the Python libraries will get installed
> AC_SUBST(PY_STD_LIB)
> PY_STD_LIB=${PyEXEC_INSTALLDIR}/lib/python${PyVERSION}
>
> # set python std library variable
> AC_SUBST(LIBS)
>
> PyLIBP=${PyEXEC_INSTALLDIR}/lib/python${PyVERSION}
>
> For those of you not familiar with autoconf, we use configure.in as the
> source file to generate the configure file.Personally, I would try and use "distutils" to make these judgements as to where things live rather than constructing the standard lib directory path from prefix and version. For example: python -c 'import distutils.sysconfig; print distutils.sysconfig.get_python_lib(plat_specific=1, standard_lib=1)' Yields: /usr/local/sys/python/lib/python2.3 On one Solaris platform I use. On Mac OS X it yields: /System/Library/Frameworks/Python.framework/Versions/2.3/lib/python2.3 Indrek, can you see what this command yields for you and whether it correctly yields what you need. Maybe it is a better of way of working this out. Graham
