Hi Davide, > On 1 Nov 2016, at 18:07, Vanzo, Davide <[email protected]> wrote: > > Hello, > I am moving this discussion over here since it is hard to follow up on the > IRC channel (I don't have a computer online 24/7 to set up a bouncer and the > time zone differential from Europe does not help either).
You could use Quassel, then you have a 'server' component that is always online, and you use a client to connect to it (talk to Pablo on the #easybuild IRC channel, he can hook you up). That doesn't fix the timezone issue though. ;-) So, it makes sense to move the discussion here. > I am trying to build ScientificPython and it fails with the following error: > > Include/Scientific/arrayobject.h:2:30: fatal error: > numpy/oldnumeric.h: No such file or directory > > The reason can be found in the fact that in toolchain.py it looks for > <base_dir>/include, <base_dir>/lib and <base_dir>/lib64 to obtain the paths > that need to be passed to the compiler. That's not entirely accurate... The toolchain mechanism does define the build environment ($CC, $CFLAGS, ...), but $CPATH (which specifies the locations that the compiler should consider for header files) is defined in the generated module files. > Although those are the default paths for the majority of programs, python > modules have a different path hierarchy and it fails because for numpy the > headers are in <base_dir>/lib/python2.7/site-packages/numpy/core/include. See > the following debug log extract for evidence. > > So, how would you suggest to proceed? One way would be to have a recursive > search starting from <base_dir> coupled with a more tight check on the > lib/include paths based not only on the directory name but also on its > content (are there .a, .o or .h files?). That would also solve the problem of > false positive entries like <numpy_base>/lib that does not contain library > files at all. I'm actually quite surprised this only pops up now... Doesn't the module file for numpy correctly define $CPATH? (can't easily check myself atm) Which easyconfig file are you using exactly? Maybe this is just an issue with a too recent numpy version being used? I seem to recall that ScientificPython requires an old version of numpy... regards, Kenneth > > Davide > > > > == 2016-11-01 12:05:51,970 toolchain.py:218 DEBUG set_variables: toolchain > variables. Do nothing. > == 2016-11-01 12:05:51,970 toolchain.py:647 DEBUG prepare: set additional > variables onlymod=False > == 2016-11-01 12:05:51,970 toolchain.py:270 DEBUG get_software_root software > root /opt/easybuild/software/Compiler/GCC/5.4.0-2.26/Python/2.7.12 for Python > was found in environment > == 2016-11-01 12:05:51,971 toolchain.py:270 DEBUG get_software_root software > root > /opt/easybuild/software/MPI/GCC/5.4.0-2.26/OpenMPI/1.10.4/numpy/1.8.2-Python-2.7.12 > for numpy was found in environment > == 2016-11-01 12:05:51,971 variables.py:542 DEBUG Passthrough to LISTCLASS > element function append_subdirs > == 2016-11-01 12:05:51,971 variables.py:267 DEBUG _is_protected: False value > None (None) > == 2016-11-01 12:05:51,971 variables.py:297 DEBUG nappend: value None > newvalue [] position None > == 2016-11-01 12:05:51,971 variables.py:186 DEBUG append_subdirs: base > /opt/easybuild/software/Compiler/GCC/5.4.0-2.26/Python/2.7.12 subdirs > ['include'] > == 2016-11-01 12:05:51,972 variables.py:198 DEBUG append_subdirs: added > directory > /opt/easybuild/software/Compiler/GCC/5.4.0-2.26/Python/2.7.12/include > == 2016-11-01 12:05:51,972 variables.py:542 DEBUG Passthrough to LISTCLASS > element function append_subdirs > == 2016-11-01 12:05:51,972 variables.py:267 DEBUG _is_protected: False value > None (None) > == 2016-11-01 12:05:51,972 variables.py:297 DEBUG nappend: value None > newvalue [] position None > == 2016-11-01 12:05:51,972 variables.py:186 DEBUG append_subdirs: base > /opt/easybuild/software/Compiler/GCC/5.4.0-2.26/Python/2.7.12 subdirs > ['lib64', 'lib'] > == 2016-11-01 12:05:51,973 variables.py:200 WARNING flags_for_subdirs: > directory /opt/easybuild/software/Compiler/GCC/5.4.0-2.26/Python/2.7.12/lib64 > was not found > == 2016-11-01 12:05:51,973 variables.py:198 DEBUG append_subdirs: added > directory /opt/easybuild/software/Compiler/GCC/5.4.0-2.26/Python/2.7.12/lib > == 2016-11-01 12:05:51,973 variables.py:542 DEBUG Passthrough to LISTCLASS > element function append_subdirs > == 2016-11-01 12:05:51,973 variables.py:267 DEBUG _is_protected: False value > None (None) > == 2016-11-01 12:05:51,973 variables.py:297 DEBUG nappend: value None > newvalue [] position None > == 2016-11-01 12:05:51,974 variables.py:186 DEBUG append_subdirs: base > /opt/easybuild/software/MPI/GCC/5.4.0-2.26/OpenMPI/1.10.4/numpy/1.8.2-Python-2.7.12 > subdirs ['include'] > == 2016-11-01 12:05:51,974 variables.py:200 WARNING flags_for_subdirs: > directory > /opt/easybuild/software/MPI/GCC/5.4.0-2.26/OpenMPI/1.10.4/numpy/1.8.2-Python-2.7.12/include > was not found > == 2016-11-01 12:05:51,974 variables.py:542 DEBUG Passthrough to LISTCLASS > element function append_subdirs > == 2016-11-01 12:05:51,974 variables.py:267 DEBUG _is_protected: False value > None (None) > == 2016-11-01 12:05:51,974 variables.py:297 DEBUG nappend: value None > newvalue [] position None > == 2016-11-01 12:05:51,975 variables.py:186 DEBUG append_subdirs: base > /opt/easybuild/software/MPI/GCC/5.4.0-2.26/OpenMPI/1.10.4/numpy/1.8.2-Python-2.7.12 > subdirs ['lib64', 'lib'] > == 2016-11-01 12:05:51,975 variables.py:200 WARNING flags_for_subdirs: > directory > /opt/easybuild/software/MPI/GCC/5.4.0-2.26/OpenMPI/1.10.4/numpy/1.8.2-Python-2.7.12/lib64 > was not found > == 2016-11-01 12:05:51,975 variables.py:198 DEBUG append_subdirs: added > directory > /opt/easybuild/software/MPI/GCC/5.4.0-2.26/OpenMPI/1.10.4/numpy/1.8.2-Python-2.7.12/lib
