include files in compatability layer may also be required

[ocaisa]

For example:

[ocaisa@node1 0.7-GCCcore-9.3.0]$ cling
In file included from input_line_1:1:
In file included from /cvmfs/pilot.eessi-hpc.org/2021.03/software/linux/x86_64/amd/zen2/software/GCCcore/9.3.0/lib/gcc/x86_64-pc-linux-gnu/9.3.0/../../../../include/c++/9.3.0/new:39:
In file included from /cvmfs/pilot.eessi-hpc.org/2021.03/software/linux/x86_64/amd/zen2/software/GCCcore/9.3.0/lib/gcc/x86_64-pc-linux-gnu/9.3.0/../../../../include/c++/9.3.0/x86_64-pc-linux-gnu/bits/c++config.h:524:
/cvmfs/pilot.eessi-hpc.org/2021.03/software/linux/x86_64/amd/zen2/software/GCCcore/9.3.0/lib/gcc/x86_64-pc-linux-gnu/9.3.0/../../../../include/c++/9.3.0/x86_64-pc-linux-gnu/bits/os_defines.h:39:10: fatal error: 'features.h' file not found
#include <features.h>
         ^~~~~~~~~~~~
Replaced symbol atexit cannot be found in JIT!
Replaced symbol at_quick_exit cannot be found in JIT!

****************** CLING ******************
* Type C++ code and press enter to run it *
*             Type .q to exit             *
*******************************************
[cling]$ .q

[ocaisa]

The more I see things like this, the more I like the idea of having a module that prepares the environment. One could imagine also including the EB settings mentioned in #59 (comment) there. If you stick to one version of such a module per toolchain generation, you can easily switch between EESSI releases on a per toolchain basis.

[ocaisa]

Hmm, I don't think this is actually a good solution. Maybe Cling is a special case? Having this variable set actually causes problems with CMake builds:

In file included from /cvmfs/pilot.eessi-hpc.org/2021.03/software/linux/x86_64/amd/zen2/software/GCCcore/9.3.0/include/c++/9.3.0/bits/stl_algo.h:59,
                 from /cvmfs/pilot.eessi-hpc.org/2021.03/software/linux/x86_64/amd/zen2/software/GCCcore/9.3.0/include/c++/9.3.0/algorithm:62,
                 from /project/60004/easybuild/build/xeuscling/0.12.1/GCCcore-9.3.0/xeus-cling-0.12.1/src/xinterpreter.cpp:10:
/cvmfs/pilot.eessi-hpc.org/2021.03/software/linux/x86_64/amd/zen2/software/GCCcore/9.3.0/include/c++/9.3.0/cstdlib:75:15: fatal error: stdlib.h: No such file or directory
   75 | #include_next <stdlib.h>

[boegel]

@ocaisa Is this still relevant?

I've just introduced 2021.12 and 2023.04 branches, and would like to get rid of the main branch.

[bedroge]

@ocaisa ping, is this still relevant?