Hi,

I'm facing the same problem when compiling OpenBabel with Python 3.6.
(creating soft links fix the OpenBabel compilation problem).

If I'm not wrong, the DPYTHON_INCLUDE_DIR is set in EB_OpenBabel easyblock:

            self.cfg['configopts'] +=
"-DPYTHON_INCLUDE_DIR=%s/include/python%s " % (root_python, shortpyver)

but that's wrong when Python is build using pymalloc casue the shortpyver
should add an extra 'm' at the end.

Python/3.6.3-foss-2017b/lib/libpython3.6m.so
and not
Python/3.6.3-foss-2017b/lib/libpython3.6.so

(Same for

self.cfg['configopts'] += "-DPYTHON_LIBRARY=%s/lib/libpython%s.%s " %
(root_python, shortpyver, shlib_ext)

the library name is libpython3.6m.so and not libpython3.6.so).

TIA,
Arnau


El mié., 25 jul. 2018 a las 15:53, Jure Pečar (<[email protected]>)
escribió:

>
> Hi all,
>
> I'm trying to build latest Boost against Python 3.7. It fails because it's
> looking for pyconfig.h at
> software/Python/3.7.0-foss-2018b/include/python3.7 while python 3.7 dropped
> its headers into software/Python/3.7.0-foss-2018b/include/python3.7m.
>
> Internet wisdom tells me that "m" suffix tells the world this python was
> built using pymalloc instead of system malloc. How should this be
> communicated to the rest of the easybuild ecosystem? Simple symlink in
> include dir? Extending CPATH in python module file? Some other ideas?
>
>
> --
>
>   Jurij Pečar
>   HPC Engineer, IT Operations, IT Services
>   EMBL Heidelberg, Meyerhofstraße 1, 69117, Heidelberg, Germany
>   Room 13-401
>

Reply via email to