One more point for the TODO for Avogadro 1.0

Moin

Sorry, it seems I cannot edit http://avogadro.openmolecules.net/wiki/To_Do

On my OpenSUSE install Avogadro doesn’t compile because of a missing Python
check. This means I need to disable python with this patch:

-OPTION(ENABLE_PYTHON “Enable python support” ON)
+OPTION(ENABLE_PYTHON “Enable python support” OFF)

The reason for this is an old lib:

/usr/lib/python2.5/config/libpython2.5.a(posixmodule.o): In function
posix_forkpty': (.text+0x3579): undefined reference toforkpty’

The CMakeFile even lists a problem with the FindPython-magic in CMake 2.4.x
and mentions that 2.6.x is superiur. I think for a 1.0 there should be a
check for Python + PythonBoost which works (eg check if the lib-version is
good enough).

Perhaps this means that for 1.0 we should depend on CMake 2.6.x as well, no
idea. KDE already dropped support for CMake 2.4.x some weeks ago (for trunk,
for KDE 4.1 CMake 2.4.6+ is still good enough).

Carsten

Carsten Niehaus wrote:

Moin

Sorry, it seems I cannot edit http://avogadro.openmolecules.net/wiki/To_Do

On my OpenSUSE install Avogadro doesn’t compile because of a missing Python
check. This means I need to disable python with this patch:

-OPTION(ENABLE_PYTHON “Enable python support” ON)
+OPTION(ENABLE_PYTHON “Enable python support” OFF)

The reason for this is an old lib:

/usr/lib/python2.5/config/libpython2.5.a(posixmodule.o): In function
posix_forkpty': (.text+0x3579): undefined reference toforkpty’

I am afraid this is an example of where the CMake devs were pretty lax
and the FindPythonLibs bugs they had in their tracker sat their for
years (if I remember right). I commented on them, many distros have
actually patched the faulty CMake files in 2.4 and 2.6. I don’t think
they necessarily fixed it in CMake 2.6 either - the individual distros
should be making CMake look in the correct place by patching their
FindPythonLibs.cmake.

The CMakeFile even lists a problem with the FindPython-magic in CMake 2.4.x
and mentions that 2.6.x is superiur. I think for a 1.0 there should be a
check for Python + PythonBoost which works (eg check if the lib-version is
good enough).

The lib version is fine - we should be using the shared object which is
not even in that directory in most distros. I patched Gentoo’s after
seeing how another distro had dealt with it. I also commented on the
relevant CMake bugs. I didn’t check whether they had fixed it properly
in CMake 2.6.1 but 2.6.0 still had the issue - looking in the wrong
directory for the shared object on the majority of distros…

Perhaps this means that for 1.0 we should depend on CMake 2.6.x as well, no
idea. KDE already dropped support for CMake 2.4.x some weeks ago (for trunk,
for KDE 4.1 CMake 2.4.6+ is still good enough).

I think that we should bump our CMake dep for the next release. On the
Mac for example Qt 4.4.0+ does not link correctly with CMake 2.4.*… I
am not sure the Python stuff is fixed in any version right now - I will
look into it later if I find the time.