Re: [easybuild] Problems building with CMake

On 12/03/2019 10:35, Jakob Schiøtz wrote: On 12 Mar 2019, at 10:25, Paul Melis wrote: You need to set CMAKE_C_COMPILER and CMAKE_CXX_COMPILER values to the full path to the compilers, not just "icc" and "icpc". CMake's error is pretty clear about it. Dear Paul, Thanks for your

Re: [easybuild] Problems building with CMake

Hi Jakob, The cleanest way would be to enhance the generic CMakeMake easyblock (cmakemake.py) so you can instruct it to specify the compiler full path (to retain backwards compatibility, in theory some things could break when specifying compilers full path rather than just using the compiler

Re: [easybuild] Problems building with CMake

> On 12 Mar 2019, at 11:03, Paul Melis wrote: > > Hi Jakob, > > Whoops, sorry, didn't read your post in enough detail. I saw the options > -DCMAKE_C_COMPILER='icc' and such and didn't expect those to come from EB > and/or the package's CMAKE. In general it is best to use full paths for

Re: AW: [easybuild] Accessing environment variables in easyconfig

Hi Stefan, "Dr. Stefan Harfst" writes: > Dear Loris, > > one way to achieve what you want is to use the modxxxfooter parameters in the > eb-file (untested): > > modluafooter = 'setenv("MCR_CACHE_ROOT", pathJoin("/scratch", > pathJoin(os.getenv("USER"), "mcr_cache")))' > modtclfooter =

Re: AW: [easybuild] Accessing environment variables in easyconfig

On 3/12/19 1:25 PM, Loris Bennett wrote: > This is not for MDCS - we don't have that. This is also the setup we > had working on our previous cluster, but where we didn't use Easybuild. > >> If you install matlab using >> env LM_LICENSE_FILE=port@host eb MATLAB...eb then the LM_LICENSE_FILE

Re: AW: [easybuild] Accessing environment variables in easyconfig

Åke Sandgren writes: > On 3/12/19 12:00 PM, Dr. Stefan Harfst wrote: >> Dear Loris, >> >> one way to achieve what you want is to use the modxxxfooter parameters in >> the eb-file (untested): >> >> modluafooter = 'setenv("MCR_CACHE_ROOT", pathJoin("/scratch", >> pathJoin(os.getenv("USER"),

Re: AW: [easybuild] Accessing environment variables in easyconfig

On 3/12/19 12:00 PM, Dr. Stefan Harfst wrote: > Dear Loris, > > one way to achieve what you want is to use the modxxxfooter parameters in the > eb-file (untested): > > modluafooter = 'setenv("MCR_CACHE_ROOT", pathJoin("/scratch", > pathJoin(os.getenv("USER"), "mcr_cache")))' > modtclfooter =

AW: [easybuild] Accessing environment variables in easyconfig

Dear Loris, one way to achieve what you want is to use the modxxxfooter parameters in the eb-file (untested): modluafooter = 'setenv("MCR_CACHE_ROOT", pathJoin("/scratch", pathJoin(os.getenv("USER"), "mcr_cache")))' modtclfooter = 'setenv("MCR_CACHE_ROOT", pathJoin("/scratch",

Re: [easybuild] resume build for software with extensions

Dear Kennet, thanks for your answer. On Fri, Mar 8, 2019 at 11:21 AM Kenneth Hoste wrote: > Dear Yann, > > On 07/03/2019 14:06, Yann Sagon wrote: > > Dear list, > > > > sometime ago, I asked this question on the same list. I think I tried > > the procedure but I'm unable to make it work again.

Re: [easybuild] Accessing environment variables in easyconfig

Hi Åke, I want to add the environment variables to a MATLAB easyconfig which are needed to run compiled MATLAB programms I tried modextravars = {'LM_LICENSE_FILE': '%s@%s' % (license_server_port, license_server), 'MATLABROOT': '.', 'MCR_HOME':

Re: [easybuild] Problems building with CMake

Hi Jakob, Whoops, sorry, didn't read your post in enough detail. I saw the options -DCMAKE_C_COMPILER='icc' and such and didn't expect those to come from EB and/or the package's CMAKE. In general it is best to use full paths for those values. Paul - Original Message - From: "Jakob

Re: [easybuild] Problems building with CMake

> On 12 Mar 2019, at 10:25, Paul Melis wrote: > > You need to set CMAKE_C_COMPILER and CMAKE_CXX_COMPILER values to the full > path to the compilers, not just "icc" and "icpc". CMake's error is pretty > clear about it. Dear Paul, Thanks for your suggestion, but are you sure? It is the

Re: [easybuild] Problems building with CMake

You need to set CMAKE_C_COMPILER and CMAKE_CXX_COMPILER values to the full path to the compilers, not just "icc" and "icpc". CMake's error is pretty clear about it. Paul I am trying to make a .eb files for a module using the CMakeMake block. I am having a strange problem, and my lack of

Re: [easybuild] Problems building with CMake

Dear Jakob, When CMake works, it's OK. When it doesn't work as you want/expect, you're in trouble... I haven't had good experiences trying to figure out why CMake does things in a particular way when something goes wrong. It looks like it's either ignoring $PATH, or maybe OpenKIMModels uses

Re: [easybuild] 5th Easybuild User Meeting

You probably know this already, but the event was also streamed and is available on Youtube: https://www.youtube.com/watch?v=P2s2p5uIY0M=2=PLhnGtSmEGEQhEjG5hD70tRwL3n58aWNHc On Tue, 12 Mar 2019 at 07:55, Kenneth Hoste mailto:kenneth.ho...@ugent.be>> wrote: Dear Jin, On 12/03/2019 02:30, Jin

[easybuild] Accessing environment variables in easyconfig

Hi, I need to get $USER within an easyconfig. I found the documentation for the Python module easybuild.tools.environment, but this doesn't seem to be what I need. Can any one point me to the documentation about how to access environment variables in an easyconfig? Cheers, Loris -- Dr.

Re: [easybuild] 5th Easybuild User Meeting

Dear Jin, On 12/03/2019 02:30, Jin Zhang wrote: Hi There, This is Jin from University of Melbourne. Looks like we just missed the 4th Easybuild User Meeting, can I ask the roughly time for 5th one? Thanks We haven't set a date yet for the next EasyBuild User Meeting, we typically only