Re: [easybuild] easybuild -devel files for users?

[Alan O'Cais]

Hmm, I'm not sure I agree that this would make the life of a user any
easier. LD_LIBRARY_PATH covers -L, CPATH covers -I and -lhdf5 you would
just have to know. I mean it's not like there are different API
implementations of HDF5 to choose from so using these new variables just
means that their build process becomes non-portable (to a non-eb
environment). I see value in the case of toolchains (which is what is
already there) since you might want to try different compiler/mpi/math
cominations but beyond that I still need some convincing...

On 26 October 2016 at 08:24, Jack Perdue  wrote:

> On 10/26/2016 12:48 AM, Jack Perdue wrote:
>
>> On 10/26/2016 12:37 AM, Alan O'Cais wrote:
>>
>>>
>>> I don't think its so simple, how would you do this for fftw where there
>>> are so many different linking options depending on what you want to do?
>>>
>>>
>> For most things (like CFLAGS), I'd at least set a sensible default and
>> then let the user
>> override in their build environment as needed.  e.g. with foss/gompi FFTW:
>>
>> EB_FFTW_INCLUDEDIRS="-I$EBROOTFFTW/include"
>> EB_FFTW_LIBDIRS="-L$EBROOTFFTW/lib"
>> EB_FFTW_LIBS="-lfftw3"
>>
>> isn't a bad start as default linkage.  With MKL, it's messier but known
>> (by EB).
>>
>>
>>
>> For X11 libs in particular, you don't need to handle it, this is why
>>> pkg-config exists (and the pkg-config paths are already baked into EB).
>>>
>>
> As to this, yes, perhaps a bad example.  But consider, say HDF5.
> Why shouldn't I have the following available (changing DIRS to FLAGS
> if that makes anyone happier):
>
> EB HDF5_INCLUDEFLAGS="-I$EBROOTHDF5/include"
> EB_HDF5_LIBFLAGS="-L$EBROOTHDF5/lib"
> EB_HDF5_LIBS="-lhdf5"
>
> jack
>
>
>
>
>>>
>>> On 25 Oct 2016 8:23 p.m., "Jack Perdue" >> j-per...@tamu.edu>> wrote:
>>>
>>> On 10/24/2016 11:42 AM, Kenneth Hoste wrote:
>>>
>>>
>>>
>>> On 23/10/16 11:59, Pablo Escobar Lopez wrote:
>>>
>>> wouldn't make sense if compiler modules provide $CC $CXX
>>> and Co. by default?
>>>
>>>
>>> It would make sense in certain cases, but not in others...
>>>
>>> This should really be up to the site to decide on this.
>>> Question is what EasyBuild v3.0 should do by default: should
>>> the toolchain module define $CC, $CFLAGS & co or not?
>>>
>>> Oh yes, and someone should modify the Toolchain easyblock to
>>> include this information in the generated module file. ;-)
>>>
>>>
>>> I'd really like to think beyond just toolchains.
>>>
>>> The new X11 bundle is a good example.
>>>
>>> We already have EBROOTX11.  Can we have
>>> EB_X11_INCLUDEDIRS, EB_X11_LIBDIRS and
>>> EB_X11_LIBS without stepping on any toes?
>>>
>>> The INCLUDEDIRS (-I) is usually easy (though not always,
>>> e.g. old versions of SparseSuite).
>>>
>>> The LIBDIRS (-L) is always questionable as to the number and or
>>> whether they have '64' in the name.
>>>
>>> Is there a reason we shouldn't have EB enumerate the 71 libraries
>>> in X11/20160819-intel-2016a/lib (with '-l' so I can drop right
>>> into a Makefile)?
>>> EB_X11_LIBS with that would be wonderful (or so I am imagining).
>>>
>>> Personally, I'd see all this done via easyconfigs (vs. easyblocks).
>>> I don't see a clear way (short of a new "modextravars" mechanism)
>>> to enable/disable per-site.  But I think keeping the ability to
>>> update
>>> those things by installers would be better without customizing
>>> Python.
>>>
>>> X11 is just one example... there are a load of others.  But providing
>>> users an easy way to build programs using EB built modules is a big
>>> bonus.
>>>
>>>
>>> jack
>>>
>>>
>>>
>>> 
>>> 
>>> 
>>> 
>>> Forschungszentrum Juelich GmbH
>>> 52425 Juelich
>>> Sitz der Gesellschaft: Juelich
>>> Eingetragen im Handelsregister des Amtsgerichts Dueren Nr. HR B 3498
>>> Vorsitzender des Aufsichtsrats: MinDir Dr. Karl Eugen Huthmacher
>>> Geschaeftsfuehrung: Prof. Dr.-Ing. Wolfgang Marquardt (Vorsitzender),
>>> Karsten Beneke (stellv. Vorsitzender), Prof. Dr.-Ing. Harald Bolt,
>>> Prof. Dr. Sebastian M. Schmidt
>>> 
>>> 
>>> 
>>> 
>>>
>>>
>>
>


-- 
Dr. Alan O'Cais
E-CAM Software Manager
Juelich Supercomputing Centre
Forschungszentrum Juelich GmbH
52425 Juelich, Germany

Phone: +49 2461 61 5213
Fax: +49 2461 61 6656
E-mail: a.oc...@fz-juelich.de
WWW:http://www.fz-juelich.de/ias/jsc/EN

Re: [easybuild] easybuild -devel files for users?

[Jack Perdue]

On 10/26/2016 12:48 AM, Jack Perdue wrote:

On 10/26/2016 12:37 AM, Alan O'Cais wrote:


I don't think its so simple, how would you do this for fftw where 
there are so many different linking options depending on what you 
want to do?




For most things (like CFLAGS), I'd at least set a sensible default and 
then let the user
override in their build environment as needed.  e.g. with foss/gompi 
FFTW:


EB_FFTW_INCLUDEDIRS="-I$EBROOTFFTW/include"
EB_FFTW_LIBDIRS="-L$EBROOTFFTW/lib"
EB_FFTW_LIBS="-lfftw3"

isn't a bad start as default linkage.  With MKL, it's messier but 
known (by EB).




For X11 libs in particular, you don't need to handle it, this is why 
pkg-config exists (and the pkg-config paths are already baked into EB).


As to this, yes, perhaps a bad example.  But consider, say HDF5.
Why shouldn't I have the following available (changing DIRS to FLAGS
if that makes anyone happier):

EB HDF5_INCLUDEFLAGS="-I$EBROOTHDF5/include"
EB_HDF5_LIBFLAGS="-L$EBROOTHDF5/lib"
EB_HDF5_LIBS="-lhdf5"

jack





On 25 Oct 2016 8:23 p.m., "Jack Perdue" > wrote:


On 10/24/2016 11:42 AM, Kenneth Hoste wrote:



On 23/10/16 11:59, Pablo Escobar Lopez wrote:

wouldn't make sense if compiler modules provide $CC $CXX
and Co. by default?


It would make sense in certain cases, but not in others...

This should really be up to the site to decide on this.
Question is what EasyBuild v3.0 should do by default: should
the toolchain module define $CC, $CFLAGS & co or not?

Oh yes, and someone should modify the Toolchain easyblock to
include this information in the generated module file. ;-)


I'd really like to think beyond just toolchains.

The new X11 bundle is a good example.

We already have EBROOTX11.  Can we have
EB_X11_INCLUDEDIRS, EB_X11_LIBDIRS and
EB_X11_LIBS without stepping on any toes?

The INCLUDEDIRS (-I) is usually easy (though not always,
e.g. old versions of SparseSuite).

The LIBDIRS (-L) is always questionable as to the number and or
whether they have '64' in the name.

Is there a reason we shouldn't have EB enumerate the 71 libraries
in X11/20160819-intel-2016a/lib (with '-l' so I can drop right
into a Makefile)?
EB_X11_LIBS with that would be wonderful (or so I am imagining).

Personally, I'd see all this done via easyconfigs (vs. easyblocks).
I don't see a clear way (short of a new "modextravars" mechanism)
to enable/disable per-site.  But I think keeping the ability to 
update
those things by installers would be better without customizing 
Python.


X11 is just one example... there are a load of others.  But 
providing

users an easy way to build programs using EB built modules is a big
bonus.


jack



 

 


Forschungszentrum Juelich GmbH
52425 Juelich
Sitz der Gesellschaft: Juelich
Eingetragen im Handelsregister des Amtsgerichts Dueren Nr. HR B 3498
Vorsitzender des Aufsichtsrats: MinDir Dr. Karl Eugen Huthmacher
Geschaeftsfuehrung: Prof. Dr.-Ing. Wolfgang Marquardt (Vorsitzender),
Karsten Beneke (stellv. Vorsitzender), Prof. Dr.-Ing. Harald Bolt,
Prof. Dr. Sebastian M. Schmidt
 

 

Re: [easybuild] easybuild -devel files for users?

[Jack Perdue]

On 10/26/2016 12:37 AM, Alan O'Cais wrote:


I don't think its so simple, how would you do this for fftw where 
there are so many different linking options depending on what you want 
to do?




For most things (like CFLAGS), I'd at least set a sensible default and 
then let the user

override in their build environment as needed.  e.g. with foss/gompi FFTW:

EB_FFTW_INCLUDEDIRS="-I$EBROOTFFTW/include"
EB_FFTW_LIBDIRS="-L$EBROOTFFTW/lib"
EB_FFTW_LIBS="-lfftw3"

isn't a bad start as default linkage.  With MKL, it's messier but known 
(by EB).


jack

For X11 libs in particular, you don't need to handle it, this is why 
pkg-config exists (and the pkg-config paths are already baked into EB).



On 25 Oct 2016 8:23 p.m., "Jack Perdue" > wrote:


On 10/24/2016 11:42 AM, Kenneth Hoste wrote:



On 23/10/16 11:59, Pablo Escobar Lopez wrote:

wouldn't make sense if compiler modules provide $CC $CXX
and Co. by default?


It would make sense in certain cases, but not in others...

This should really be up to the site to decide on this.
Question is what EasyBuild v3.0 should do by default: should
the toolchain module define $CC, $CFLAGS & co or not?

Oh yes, and someone should modify the Toolchain easyblock to
include this information in the generated module file. ;-)


I'd really like to think beyond just toolchains.

The new X11 bundle is a good example.

We already have EBROOTX11.  Can we have
EB_X11_INCLUDEDIRS, EB_X11_LIBDIRS and
EB_X11_LIBS without stepping on any toes?

The INCLUDEDIRS (-I) is usually easy (though not always,
e.g. old versions of SparseSuite).

The LIBDIRS (-L) is always questionable as to the number and or
whether they have '64' in the name.

Is there a reason we shouldn't have EB enumerate the 71 libraries
in X11/20160819-intel-2016a/lib (with '-l' so I can drop right
into a Makefile)?
EB_X11_LIBS with that would be wonderful (or so I am imagining).

Personally, I'd see all this done via easyconfigs (vs. easyblocks).
I don't see a clear way (short of a new "modextravars" mechanism)
to enable/disable per-site.  But I think keeping the ability to update
those things by installers would be better without customizing Python.

X11 is just one example... there are a load of others.  But providing
users an easy way to build programs using EB built modules is a big
bonus.


jack





Forschungszentrum Juelich GmbH
52425 Juelich
Sitz der Gesellschaft: Juelich
Eingetragen im Handelsregister des Amtsgerichts Dueren Nr. HR B 3498
Vorsitzender des Aufsichtsrats: MinDir Dr. Karl Eugen Huthmacher
Geschaeftsfuehrung: Prof. Dr.-Ing. Wolfgang Marquardt (Vorsitzender),
Karsten Beneke (stellv. Vorsitzender), Prof. Dr.-Ing. Harald Bolt,
Prof. Dr. Sebastian M. Schmidt

Re: [easybuild] easybuild -devel files for users?

[Alan O'Cais]

I don't think its so simple, how would you do this for fftw where there are so 
many different linking options depending on what you want to do?

For X11 libs in particular, you don't need to handle it, this is why pkg-config 
exists (and the pkg-config paths are already baked into EB).

On 25 Oct 2016 8:23 p.m., "Jack Perdue" 
mailto:j-per...@tamu.edu>> wrote:
On 10/24/2016 11:42 AM, Kenneth Hoste wrote:


On 23/10/16 11:59, Pablo Escobar Lopez wrote:
wouldn't make sense if compiler modules provide $CC $CXX and Co. by default?

It would make sense in certain cases, but not in others...

This should really be up to the site to decide on this.
Question is what EasyBuild v3.0 should do by default: should the toolchain 
module define $CC, $CFLAGS & co or not?

Oh yes, and someone should modify the Toolchain easyblock to include this 
information in the generated module file. ;-)


I'd really like to think beyond just toolchains.

The new X11 bundle is a good example.

We already have EBROOTX11.  Can we have
EB_X11_INCLUDEDIRS, EB_X11_LIBDIRS and
EB_X11_LIBS without stepping on any toes?

The INCLUDEDIRS (-I) is usually easy (though not always,
e.g. old versions of SparseSuite).

The LIBDIRS (-L) is always questionable as to the number and or
whether they have '64' in the name.

Is there a reason we shouldn't have EB enumerate the 71 libraries
in X11/20160819-intel-2016a/lib (with '-l' so I can drop right into a Makefile)?
EB_X11_LIBS with that would be wonderful (or so I am imagining).

Personally, I'd see all this done via easyconfigs (vs. easyblocks).
I don't see a clear way (short of a new "modextravars" mechanism)
to enable/disable per-site.  But I think keeping the ability to update
those things by installers would be better without customizing Python.

X11 is just one example... there are a load of others.  But providing
users an easy way to build programs using EB built modules is a big
bonus.


jack





Forschungszentrum Juelich GmbH
52425 Juelich
Sitz der Gesellschaft: Juelich
Eingetragen im Handelsregister des Amtsgerichts Dueren Nr. HR B 3498
Vorsitzender des Aufsichtsrats: MinDir Dr. Karl Eugen Huthmacher
Geschaeftsfuehrung: Prof. Dr.-Ing. Wolfgang Marquardt (Vorsitzender),
Karsten Beneke (stellv. Vorsitzender), Prof. Dr.-Ing. Harald Bolt,
Prof. Dr. Sebastian M. Schmidt

Re: [easybuild] easybuild -devel files for users?

[Jack Perdue]

On 10/24/2016 11:42 AM, Kenneth Hoste wrote:



On 23/10/16 11:59, Pablo Escobar Lopez wrote:
wouldn't make sense if compiler modules provide $CC $CXX and Co. by 
default?


It would make sense in certain cases, but not in others...

This should really be up to the site to decide on this.
Question is what EasyBuild v3.0 should do by default: should the 
toolchain module define $CC, $CFLAGS & co or not?


Oh yes, and someone should modify the Toolchain easyblock to include 
this information in the generated module file. ;-)




I'd really like to think beyond just toolchains.

The new X11 bundle is a good example.

We already have EBROOTX11.  Can we have
EB_X11_INCLUDEDIRS, EB_X11_LIBDIRS and
EB_X11_LIBS without stepping on any toes?

The INCLUDEDIRS (-I) is usually easy (though not always,
e.g. old versions of SparseSuite).

The LIBDIRS (-L) is always questionable as to the number and or
whether they have '64' in the name.

Is there a reason we shouldn't have EB enumerate the 71 libraries
in X11/20160819-intel-2016a/lib (with '-l' so I can drop right into a 
Makefile)?

EB_X11_LIBS with that would be wonderful (or so I am imagining).

Personally, I'd see all this done via easyconfigs (vs. easyblocks).
I don't see a clear way (short of a new "modextravars" mechanism)
to enable/disable per-site.  But I think keeping the ability to update
those things by installers would be better without customizing Python.

X11 is just one example... there are a load of others.  But providing
users an easy way to build programs using EB built modules is a big
bonus.


jack

RE: [easybuild] easybuild -devel files for users?

[Siddiqui, Shahzeb]

Pablo,

I wanted to share some insight on some differences between intel’s easybuild 
file and what you get by using compilervar.sh to get the environment.  The 
values CC, CXX are not defined by intel maybe for some good reason, not sure 
why. As for CFLAGS I don’t think that should be defined because different 
programs need to compile with different flags and defining CFLAGS can cause 
some issues. CC, CXX could be done according to Lmod’s use of pushenv see 
https://www.tacc.utexas.edu/research-development/tacc-projects/lmod/advanced-user-guide/more-about-writing-module-files

I found documentation on intel 2015 Parallel Studio Page 20 tells you do use 
compilervar.sh 
http://www.ritme.com/uploads/assets/FAQ/Intel/Release_Notes_C_2015_L_EN_initial_product.pdf

I have seen this documentation for Intel 2016, and I presume it is same for 
2017. I have attached a copy of modulefile from easybuild and compilervars.sh, 
there are lots of differences that need to be accounted.

This link 
https://software.intel.com/en-us/articles/using-environment-modules-with-the-intel-development-tools
 tells you how to create modulefile from shell script using env2 utility. This 
is how I got my modulefile for intel-17-compilervar. I am using this in my 
easybuild, unfortunately when I run easybuild it generates the default intel 
modulefile so I have to overwrite with mine. Intel does not make use of CC 
CFLAGS variable.

It seems like Makefile variables defined inside the file override ones in the 
environment. I tried a simple example of Makefile to see what happens.

[hpcswadm@hpcv18 ~]$ make
gcc a.c;
[hpcswadm@hpcv18 ~]$ echo $CC
pgcc

[hpcswadm@hpcv18 ~]$ cat Makefile
CC=gcc

all:
$(CC) a.c;
clean:
rm a.out
[hpcswadm@hpcv18 ~]$ ml

Currently Loaded Modules:
  1) pgi/16.4

[hpcswadm@hpcv18 ~]$ ml show pgi
-
   /nfs/grid/software/RHEL7/pfizer-modules/all/pgi/16.4.lua:
-
pushenv("CC","pgcc")
pushenv("FC","pgfortran")
pushenv("CXX","pgcxx")
pushenv("F77","pgf77")




From this experiment, I can conclude if your intent is to use $CC $CXX for 
building software then, I would be careful with hardcoded Makefile that have CC 
defined. Whereas configure script accurately pick up $CC if defined. I think 
for this reason, $CC is not defined by most compilers for instance gcc and 
intel don’t redefine $CC to gcc or icc. That being said, you can potentially 
intermix compilers if some Makefile have $CC defined in file while configure 
might define CC from environment. It would depend on each site if your intent 
is to use $CC for users to compile code then it might be okay, however if they 
are using to build software with complicated Makefile structure and they 
redefine $CC inside then it should not be used.


From: easybuild-requ...@lists.ugent.be 
[mailto:easybuild-requ...@lists.ugent.be] On Behalf Of Kenneth Hoste
Sent: Monday, October 24, 2016 12:42 PM
To: easybuild@lists.ugent.be
Subject: Re: [easybuild] easybuild -devel files for users?


On 23/10/16 11:59, Pablo Escobar Lopez wrote:
wouldn't make sense if compiler modules provide $CC $CXX and Co. by default?

It would make sense in certain cases, but not in others...

This should really be up to the site to decide on this.
Question is what EasyBuild v3.0 should do by default: should the toolchain 
module define $CC, $CFLAGS & co or not?

Oh yes, and someone should modify the Toolchain easyblock to include this 
information in the generated module file. ;-)


K.




2016-10-22 23:59 GMT+02:00 Alan O'Cais 
mailto:a.oc...@fz-juelich.de>>:

Maybe I'm misunderstanding but that is pretty much exactly why I 'created' the 
trivial buildenv easyblock. The users just load the module that gets created  
and they can simply use $CC and friends in their build processes, making 
switching toolchains very straightforward.

On 22 Oct 2016 4:09 p.m., "Vanzo, Davide" 
mailto:davide.va...@vanderbilt.edu>> wrote:
From a user perspective it would be more interesting to have this option under 
Lmod than EB. The end user is most likely to interact only with the environment 
modules manager than EB directly. The idea would be that the user loads all the 
modules he/she needs according to a specific toolchain and can get all the 
linking flags by calling something like:

$module -L

In this way the user can use command substitution directly into Makefiles. More 
importantly, this should also take into account ordering the lib flags 
accordingly since someti

Re: [easybuild] easybuild -devel files for users?

[Miguel Dias Costa]

On 25/10/16 00:42, Kenneth Hoste wrote:


On 23/10/16 11:59, Pablo Escobar Lopez wrote:
wouldn't make sense if compiler modules provide $CC $CXX and Co. by 
default?


It would make sense in certain cases, but not in others...

This should really be up to the site to decide on this.
Question is what EasyBuild v3.0 should do by default: should the 
toolchain module define $CC, $CFLAGS & co or not?


From the perspective of someone who is still not that familiar with 
EasyBuild, I'd say that at first I did expect the toolchain module to 
set the build environment, but eventually got used to thinking of it as 
a runtime environment.


This makes sense when you're always using eb to build, since it takes 
care of setting up the buildenv, but not when you need to build 
something "manually". Admins should probably always try to use eb but 
for users it may not be worth the learning curve, setting up their own 
install paths, etc., they just want to use the globally installed modules.


What about simply installing Alan's buildenv module by default everytime 
a toolchain is installed? This doesn't break anything or change expected 
behaviour while making the build environment readily available.


Additionally, if the module name is something like 
toolchainname-buildenv, or -devel, so that it appears right next to the 
toolchain module in the list, it should make everything clearer for 
everyone... or am I oversimplifying?


Miguel



Oh yes, and someone should modify the Toolchain easyblock to include 
this information in the generated module file. ;-)



K.




2016-10-22 23:59 GMT+02:00 Alan O'Cais >:


Maybe I'm misunderstanding but that is pretty much exactly why I
'created' the trivial buildenv easyblock. The users just load the
module that gets created  and they can simply use $CC and friends
in their build processes, making switching toolchains very
straightforward.


On 22 Oct 2016 4:09 p.m., "Vanzo, Davide"
mailto:davide.va...@vanderbilt.edu>> wrote:

From a user perspective it would be more interesting to have
this option under Lmod than EB. The end user is most likely
to interact only with the environment modules manager than EB
directly. The idea would be that the user loads all the
modules he/she needs according to a specific toolchain and
can get all the linking flags by calling something like:

$module -L
In this way the user can use command substitution directly
into Makefiles. More importantly, this should also take into
account ordering the lib flags accordingly since sometimes
order is essential for successful linking.
That is something that we discussed internally since this
functionality is provided by our current modules manager
(although in a very primitive way) and would be lost when
transitioning to Lmod.

-- 
Davide Vanzo, PhD

Application Developer
Adjunct Assistant Professor of Chemical and Biomolecular
Engineering
Advanced Computing Center for Research and Education (ACCRE)
Vanderbilt University - Hill Center 201
(615)-875-9137 
www.accre.vanderbilt.edu 

On Oct 22 2016, at 8:12 am, Jack Perdue mailto:j-per...@tamu.edu>> wrote:

On 10/22/2016 02:47 AM, Kenneth Hoste wrote:
> Hi Jack,
>
> On 21/10/16 02:46, Jack Perdue wrote:
>> Howdy EB gods (Ken and crew),
>>
>> So EB, puts some useful environment settings in
>> //easybuild/*-devel
>>
>> Is there a way to utilize those variables when not
>> using EB?
>>
>> For example, I assume that if a user loads icc that they
>> more than likely would like CC=icc (CFLAGS is a different
>> matter).
>>
>> But EB doesn't do that now (probably for good reason).
>
> It doesn't right now, no, but would it be interesting
to add an option
> to include statements to define the build environment
as used by
> EasyBuild in the toolchain module?
>
> You can argue for it both ways, it's just a matter of
what EasyBuild
> should do by default (and we currently have a window of
opportunity to
> change the default behavior with EasyBuild 3.0 being
the next release).

I'd definitely like to see it as an option. For testing,
--dump-env-script on
ImageMagick-7.0.3-2-intel-2016b.eb would be a good start.
I'd like to
see _everything_ set in that .env instead set in the
modules first... as
just a
start.

Beyond that, I'd a

Re: [easybuild] easybuild -devel files for users?

[Kenneth Hoste]

On 23/10/16 11:59, Pablo Escobar Lopez wrote:
wouldn't make sense if compiler modules provide $CC $CXX and Co. by 
default?


It would make sense in certain cases, but not in others...

This should really be up to the site to decide on this.
Question is what EasyBuild v3.0 should do by default: should the 
toolchain module define $CC, $CFLAGS & co or not?


Oh yes, and someone should modify the Toolchain easyblock to include 
this information in the generated module file. ;-)



K.




2016-10-22 23:59 GMT+02:00 Alan O'Cais >:


Maybe I'm misunderstanding but that is pretty much exactly why I
'created' the trivial buildenv easyblock. The users just load the
module that gets created  and they can simply use $CC and friends
in their build processes, making switching toolchains very
straightforward.


On 22 Oct 2016 4:09 p.m., "Vanzo, Davide"
mailto:davide.va...@vanderbilt.edu>>
wrote:

From a user perspective it would be more interesting to have
this option under Lmod than EB. The end user is most likely to
interact only with the environment modules manager than EB
directly. The idea would be that the user loads all the
modules he/she needs according to a specific toolchain and can
get all the linking flags by calling something like:

$module -L
In this way the user can use command substitution directly
into Makefiles. More importantly, this should also take into
account ordering the lib flags accordingly since sometimes
order is essential for successful linking.
That is something that we discussed internally since this
functionality is provided by our current modules manager
(although in a very primitive way) and would be lost when
transitioning to Lmod.

-- 
Davide Vanzo, PhD

Application Developer
Adjunct Assistant Professor of Chemical and Biomolecular
Engineering
Advanced Computing Center for Research and Education (ACCRE)
Vanderbilt University - Hill Center 201
(615)-875-9137 
www.accre.vanderbilt.edu 

On Oct 22 2016, at 8:12 am, Jack Perdue mailto:j-per...@tamu.edu>> wrote:

On 10/22/2016 02:47 AM, Kenneth Hoste wrote:
> Hi Jack,
>
> On 21/10/16 02:46, Jack Perdue wrote:
>> Howdy EB gods (Ken and crew),
>>
>> So EB, puts some useful environment settings in
>> //easybuild/*-devel
>>
>> Is there a way to utilize those variables when not
>> using EB?
>>
>> For example, I assume that if a user loads icc that they
>> more than likely would like CC=icc (CFLAGS is a different
>> matter).
>>
>> But EB doesn't do that now (probably for good reason).
>
> It doesn't right now, no, but would it be interesting to
add an option
> to include statements to define the build environment as
used by
> EasyBuild in the toolchain module?
>
> You can argue for it both ways, it's just a matter of
what EasyBuild
> should do by default (and we currently have a window of
opportunity to
> change the default behavior with EasyBuild 3.0 being the
next release).

I'd definitely like to see it as an option. For testing,
--dump-env-script on
ImageMagick-7.0.3-2-intel-2016b.eb would be a good start.
I'd like to
see _everything_ set in that .env instead set in the
modules first... as
just a
start.

Beyond that, I'd also like to see a line with -lX11 -lXabc
-lX123 so I
don't need to
remember the name of all the X11 libs.

But it should be a site (or user) selectable option (I
could see some
people not wanting such things).


jack (who won't be making it to Utah but does have new
cluster coming online
 and has the ability to provide beer through his
agents)







Forschungszentrum Juelich GmbH
52425 Juelich
Sitz der Gesellschaft: Juelich
Eingetragen im Handelsregister des Amtsgerichts Dueren Nr. HR B 3498
Vorsitzender des Aufsichtsrats: MinDir Dr. Karl Eugen Huthmacher
Geschaeftsfuehrung: Prof. Dr.-Ing. Wolfgang Marquardt (Vorsitzender),
Karsten Beneke (stellv. Vorsitzender), Prof. Dr.-Ing. Harald Bolt,
Prof. Dr. Sebastian M. Schmi

Re: [easybuild] easybuild -devel files for users?

[Pablo Escobar Lopez]

wouldn't make sense if compiler modules provide $CC $CXX and Co. by
default?



2016-10-22 23:59 GMT+02:00 Alan O'Cais :

> Maybe I'm misunderstanding but that is pretty much exactly why I 'created'
> the trivial buildenv easyblock. The users just load the module that gets
> created  and they can simply use $CC and friends in their build processes,
> making switching toolchains very straightforward.
>
> On 22 Oct 2016 4:09 p.m., "Vanzo, Davide" 
> wrote:
>
>> From a user perspective it would be more interesting to have this option
>> under Lmod than EB. The end user is most likely to interact only with the
>> environment modules manager than EB directly. The idea would be that the
>> user loads all the modules he/she needs according to a specific
>> toolchain and can get all the linking flags by calling something like:
>>
>> $module -L
>>
>> In this way the user can use command substitution directly into
>> Makefiles. More importantly, this should also take into account ordering
>> the lib flags accordingly since sometimes order is essential for
>> successful linking.
>> That is something that we discussed internally since this functionality
>> is provided by our current modules manager (although in a very primitive
>> way) and would be lost when transitioning to Lmod.
>>
>> --
>> Davide Vanzo, PhD
>> Application Developer
>> Adjunct Assistant Professor of Chemical and Biomolecular Engineering
>> Advanced Computing Center for Research and Education (ACCRE)
>> Vanderbilt University - Hill Center 201
>> (615)-875-9137
>> www.accre.vanderbilt.edu
>>
>> On Oct 22 2016, at 8:12 am, Jack Perdue  wrote:
>>
>>> On 10/22/2016 02:47 AM, Kenneth Hoste wrote:
>>> > Hi Jack,
>>> >
>>> > On 21/10/16 02:46, Jack Perdue wrote:
>>> >> Howdy EB gods (Ken and crew),
>>> >>
>>> >> So EB, puts some useful environment settings in
>>> >> //easybuild/*-devel
>>> >>
>>> >> Is there a way to utilize those variables when not
>>> >> using EB?
>>> >>
>>> >> For example, I assume that if a user loads icc that they
>>> >> more than likely would like CC=icc (CFLAGS is a different
>>> >> matter).
>>> >>
>>> >> But EB doesn't do that now (probably for good reason).
>>> >
>>> > It doesn't right now, no, but would it be interesting to add an option
>>> > to include statements to define the build environment as used by
>>> > EasyBuild in the toolchain module?
>>> >
>>> > You can argue for it both ways, it's just a matter of what EasyBuild
>>> > should do by default (and we currently have a window of opportunity to
>>> > change the default behavior with EasyBuild 3.0 being the next release).
>>>
>>> I'd definitely like to see it as an option. For testing,
>>> --dump-env-script on
>>> ImageMagick-7.0.3-2-intel-2016b.eb would be a good start. I'd like to
>>> see _everything_ set in that .env instead set in the modules first... as
>>> just a
>>> start.
>>>
>>> Beyond that, I'd also like to see a line with -lX11 -lXabc -lX123 so I
>>> don't need to
>>> remember the name of all the X11 libs.
>>>
>>> But it should be a site (or user) selectable option (I could see some
>>> people not wanting such things).
>>>
>>>
>>> jack (who won't be making it to Utah but does have new cluster coming
>>> online
>>>  and has the ability to provide beer through his agents)
>>>
>>
>
> 
> 
> 
> 
> Forschungszentrum Juelich GmbH
> 52425 Juelich
> Sitz der Gesellschaft: Juelich
> Eingetragen im Handelsregister des Amtsgerichts Dueren Nr. HR B 3498
> Vorsitzender des Aufsichtsrats: MinDir Dr. Karl Eugen Huthmacher
> Geschaeftsfuehrung: Prof. Dr.-Ing. Wolfgang Marquardt (Vorsitzender),
> Karsten Beneke (stellv. Vorsitzender), Prof. Dr.-Ing. Harald Bolt,
> Prof. Dr. Sebastian M. Schmidt
> 
> 
> 
> 
>
>


-- 
Pablo Escobar López
HPC systems engineer
sciCORE, University of Basel
SIB Swiss Institute of Bioinformatics
http://scicore.unibas.ch

Re: [easybuild] easybuild -devel files for users?

[Alan O'Cais]

Maybe I'm misunderstanding but that is pretty much exactly why I 'created' the 
trivial buildenv easyblock. The users just load the module that gets created  
and they can simply use $CC and friends in their build processes, making 
switching toolchains very straightforward.

On 22 Oct 2016 4:09 p.m., "Vanzo, Davide" 
mailto:davide.va...@vanderbilt.edu>> wrote:
>From a user perspective it would be more interesting to have this option under 
>Lmod than EB. The end user is most likely to interact only with the 
>environment modules manager than EB directly. The idea would be that the user 
>loads all the modules he/she needs according to a specific toolchain and can 
>get all the linking flags by calling something like:

$module -L

In this way the user can use command substitution directly into Makefiles. More 
importantly, this should also take into account ordering the lib flags 
accordingly since sometimes order is essential for successful linking.
That is something that we discussed internally since this functionality is 
provided by our current modules manager (although in a very primitive way) and 
would be lost when transitioning to Lmod.

--
Davide Vanzo, PhD
Application Developer
Adjunct Assistant Professor of Chemical and Biomolecular Engineering
Advanced Computing Center for Research and Education (ACCRE)
Vanderbilt University - Hill Center 201
(615)-875-9137
www.accre.vanderbilt.edu

On Oct 22 2016, at 8:12 am, Jack Perdue 
mailto:j-per...@tamu.edu>> wrote:

On 10/22/2016 02:47 AM, Kenneth Hoste wrote:
> Hi Jack,
>
> On 21/10/16 02:46, Jack Perdue wrote:
>> Howdy EB gods (Ken and crew),
>>
>> So EB, puts some useful environment settings in
>> //easybuild/*-devel
>>
>> Is there a way to utilize those variables when not
>> using EB?
>>
>> For example, I assume that if a user loads icc that they
>> more than likely would like CC=icc (CFLAGS is a different
>> matter).
>>
>> But EB doesn't do that now (probably for good reason).
>
> It doesn't right now, no, but would it be interesting to add an option
> to include statements to define the build environment as used by
> EasyBuild in the toolchain module?
>
> You can argue for it both ways, it's just a matter of what EasyBuild
> should do by default (and we currently have a window of opportunity to
> change the default behavior with EasyBuild 3.0 being the next release).

I'd definitely like to see it as an option. For testing,
--dump-env-script on
ImageMagick-7.0.3-2-intel-2016b.eb would be a good start. I'd like to
see _everything_ set in that .env instead set in the modules first... as
just a
start.

Beyond that, I'd also like to see a line with -lX11 -lXabc -lX123 so I
don't need to
remember the name of all the X11 libs.

But it should be a site (or user) selectable option (I could see some
people not wanting such things).

jack (who won't be making it to Utah but does have new cluster coming online
 and has the ability to provide beer through his agents)




Forschungszentrum Juelich GmbH
52425 Juelich
Sitz der Gesellschaft: Juelich
Eingetragen im Handelsregister des Amtsgerichts Dueren Nr. HR B 3498
Vorsitzender des Aufsichtsrats: MinDir Dr. Karl Eugen Huthmacher
Geschaeftsfuehrung: Prof. Dr.-Ing. Wolfgang Marquardt (Vorsitzender),
Karsten Beneke (stellv. Vorsitzender), Prof. Dr.-Ing. Harald Bolt,
Prof. Dr. Sebastian M. Schmidt

Re: [easybuild] easybuild -devel files for users?

[Vanzo, Davide]

Absolutely. Just trying to get a feeling on your thoughts about this potential 
broader implementation of the functionality.

DV

On October 22, 2016 10:38:08 Jack Perdue  wrote:

On 10/22/2016 09:09 AM, Vanzo, Davide wrote:

>From a user perspective it would be more interesting to have this
option under Lmod than EB. The end user is most likely to interact
only with the environment modules manager than EB directly. The idea
would be that the user loads all the modules he/she needs according to
a specific toolchain and can get all the linking flags by calling
something like:

$module -L
In this way the user can use command substitution directly into
Makefiles. More importantly, this should also take into account
ordering the lib flags accordingly since sometimes order is essential
for successful linking.
That is something that we discussed internally since this
functionality is provided by our current modules manager (although in
a very primitive way) and would be lost when transitioning to Lmod.

That would all be up to Robert for the most part.
But even if such an option existed it would still need
EB to feed it what it needs to work.

jack

Re: [easybuild] easybuild -devel files for users?

[Jack Perdue]

On 10/22/2016 09:09 AM, Vanzo, Davide wrote:
From a user perspective it would be more interesting to have this 
option under Lmod than EB. The end user is most likely to interact 
only with the environment modules manager than EB directly. The idea 
would be that the user loads all the modules he/she needs according to 
a specific toolchain and can get all the linking flags by calling 
something like:


$module -L
In this way the user can use command substitution directly into 
Makefiles. More importantly, this should also take into account 
ordering the lib flags accordingly since sometimes order is essential 
for successful linking.
That is something that we discussed internally since this 
functionality is provided by our current modules manager (although in 
a very primitive way) and would be lost when transitioning to Lmod.


That would all be up to Robert for the most part.
But even if such an option existed it would still need
EB to feed it what it needs to work.

jack

Re: [easybuild] easybuild -devel files for users?

[Vanzo, Davide]

From a user perspective it would be more interesting to have this option under 
Lmod than EB. The end user is most likely to interact only with the environment 
modules manager than EB directly. The idea would be that the user loads all the 
modules he/she needs according to a specific toolchain and can get all the 
linking flags by calling something like:

$module -L

In this way the user can use command substitution directly into Makefiles. More 
importantly, this should also take into account ordering the lib flags 
accordingly since sometimes order is essential for successful linking.
That is something that we discussed internally since this functionality is 
provided by our current modules manager (although in a very primitive way) and 
would be lost when transitioning to Lmod.

--
Davide Vanzo, PhD
Application Developer
Adjunct Assistant Professor of Chemical and Biomolecular Engineering
Advanced Computing Center for Research and Education (ACCRE)
Vanderbilt University - Hill Center 201
(615)-875-9137
www.accre.vanderbilt.edu

On Oct 22 2016, at 8:12 am, Jack Perdue  wrote:

On 10/22/2016 02:47 AM, Kenneth Hoste wrote:
> Hi Jack,
>
> On 21/10/16 02:46, Jack Perdue wrote:
>> Howdy EB gods (Ken and crew),
>>
>> So EB, puts some useful environment settings in
>> //easybuild/*-devel
>>
>> Is there a way to utilize those variables when not
>> using EB?
>>
>> For example, I assume that if a user loads icc that they
>> more than likely would like CC=icc (CFLAGS is a different
>> matter).
>>
>> But EB doesn't do that now (probably for good reason).
>
> It doesn't right now, no, but would it be interesting to add an option
> to include statements to define the build environment as used by
> EasyBuild in the toolchain module?
>
> You can argue for it both ways, it's just a matter of what EasyBuild
> should do by default (and we currently have a window of opportunity to
> change the default behavior with EasyBuild 3.0 being the next release).

I'd definitely like to see it as an option. For testing,
--dump-env-script on
ImageMagick-7.0.3-2-intel-2016b.eb would be a good start. I'd like to
see _everything_ set in that .env instead set in the modules first... as
just a
start.

Beyond that, I'd also like to see a line with -lX11 -lXabc -lX123 so I
don't need to
remember the name of all the X11 libs.

But it should be a site (or user) selectable option (I could see some
people not wanting such things).

jack (who won't be making it to Utah but does have new cluster coming online
 and has the ability to provide beer through his agents)

Re: [easybuild] easybuild -devel files for users?

[Jack Perdue]

On 10/22/2016 02:47 AM, Kenneth Hoste wrote:

Hi Jack,

On 21/10/16 02:46, Jack Perdue wrote:

Howdy EB gods (Ken and crew),

So EB, puts some useful environment settings in
//easybuild/*-devel

Is there a way to utilize those variables when not
using EB?

For example, I assume that if a user loads icc that they
more than likely would like CC=icc (CFLAGS is a different
matter).

But EB doesn't do that now (probably for good reason).


It doesn't right now, no, but would it be interesting to add an option 
to include statements to define the build environment as used by 
EasyBuild in the toolchain module?


You can argue for it both ways, it's just a matter of what EasyBuild 
should do by default (and we currently have a window of opportunity to 
change the default behavior with EasyBuild 3.0 being the next release).


I'd definitely like to see it as an option.  For testing, 
--dump-env-script on

ImageMagick-7.0.3-2-intel-2016b.eb would be a good start.  I'd like to
see _everything_ set in that .env instead set in the modules first... as 
just a

start.

Beyond that,  I'd also like to see a line with -lX11 -lXabc -lX123 so I 
don't need to

remember the name of all the X11 libs.

But it should be a site (or user) selectable option (I could see some
people not wanting such things).


jack (who won't be making it to Utah but does have new cluster coming online
and has the ability to provide beer through his agents)

Re: [easybuild] easybuild -devel files for users?

[Kenneth Hoste]

On 22/10/16 09:41, Kenneth Hoste wrote:

Hi all,

Neither --dump-env-script nor the use of the BuildEnv easyblock are 
currently covered in the documentation.


Anyone up for writing a small page on "Making the EasyBuild build 
environment accessible to users" to go under "Advanced usage topics"?


Here's a head start: https://github.com/hpcugent/easybuild/pull/263 .

Anyone up for helping out to flesh this out?


regards,

Kenneth




regards,

Kenneth

On 21/10/16 07:03, Miguel Dias Costa wrote:


that looks even better, good to know!

On 21/10/16 12:25, Alan O'Cais wrote:


There's also an easyblock to create a module filled with the 
environment variables used by a tool chain during the build process, 
an example use is at

https://github.com/hpcugent/easybuild-easyconfigs/tree/master/easybuild/easyconfigs/b/buildenv


On 21 Oct 2016 3:10 a.m., "Jack Perdue" > wrote:


Howdy Miguel,

I totally missed that in some release notes along the way.
That's awesome.  Thanks! (to Miguel and all those that made
it possible)

jack (seeing it of great use to our users)


On 10/20/2016 08:02 PM, Miguel Dias Costa wrote:

Dear Jack,

I sometimes use --dump-env-script [1] (on the .eb files, not
the -devel files)

Miguel

[1]
https://github.com/hpcugent/easybuild-framework/pull/1624



On 21/10/16 08:46, Jack Perdue wrote:

Howdy EB gods (Ken and crew),

So EB, puts some useful environment settings in
//easybuild/*-devel

Is there a way to utilize those variables when not
using EB?

For example, I assume that if a user loads icc that they
more than likely would like CC=icc (CFLAGS is a different
matter).

But EB doesn't do that now (probably for good reason).

But it WOULD be nice if I could somehow use the variables in
the -devel file (in bash) without all the extraneous stuff.

EB has a rich collection of useful environment variables
(especially when using Intel toolchains ala
FFTW/LAPACK/BLAS)
how can we make them available to the user (who just
wants to
compile against EB modules without using EB).






Forschungszentrum Juelich GmbH
52425 Juelich
Sitz der Gesellschaft: Juelich
Eingetragen im Handelsregister des Amtsgerichts Dueren Nr. HR B 3498
Vorsitzender des Aufsichtsrats: MinDir Dr. Karl Eugen Huthmacher
Geschaeftsfuehrung: Prof. Dr.-Ing. Wolfgang Marquardt (Vorsitzender),
Karsten Beneke (stellv. Vorsitzender), Prof. Dr.-Ing. Harald Bolt,
Prof. Dr. Sebastian M. Schmidt

Re: [easybuild] easybuild -devel files for users?

[Kenneth Hoste]

Hi Jack,

On 21/10/16 02:46, Jack Perdue wrote:

Howdy EB gods (Ken and crew),

So EB, puts some useful environment settings in
//easybuild/*-devel

Is there a way to utilize those variables when not
using EB?

For example, I assume that if a user loads icc that they
more than likely would like CC=icc (CFLAGS is a different
matter).

But EB doesn't do that now (probably for good reason).


It doesn't right now, no, but would it be interesting to add an option 
to include statements to define the build environment as used by 
EasyBuild in the toolchain module?


You can argue for it both ways, it's just a matter of what EasyBuild 
should do by default (and we currently have a window of opportunity to 
change the default behavior with EasyBuild 3.0 being the next release).



But it WOULD be nice if I could somehow use the variables in
the -devel file (in bash) without all the extraneous stuff.


Well, the devel modules were originally supposed to cover this need, but 
they got broken a long time ago an nobody has cared enough to fix it 
(even though, yes Markus, I'm going to say it, it shouldn't be hard to 
fix those problems).



EB has a rich collection of useful environment variables
(especially when using Intel toolchains ala FFTW/LAPACK/BLAS)
how can we make them available to the user (who just wants to
compile against EB modules without using EB).


As already mentioned by Miguel and Alan: --dump-env-script and the 
BuildEnv generic easyblock could fulfill your need.



regards,

Kenneth

Re: [easybuild] easybuild -devel files for users?

[Kenneth Hoste]

Hi all,

Neither --dump-env-script nor the use of the BuildEnv easyblock are 
currently covered in the documentation.


Anyone up for writing a small page on "Making the EasyBuild build 
environment accessible to users" to go under "Advanced usage topics"?



regards,

Kenneth

On 21/10/16 07:03, Miguel Dias Costa wrote:


that looks even better, good to know!

On 21/10/16 12:25, Alan O'Cais wrote:


There's also an easyblock to create a module filled with the 
environment variables used by a tool chain during the build process, 
an example use is at

https://github.com/hpcugent/easybuild-easyconfigs/tree/master/easybuild/easyconfigs/b/buildenv


On 21 Oct 2016 3:10 a.m., "Jack Perdue" > wrote:


Howdy Miguel,

I totally missed that in some release notes along the way.
That's awesome.  Thanks! (to Miguel and all those that made
it possible)

jack (seeing it of great use to our users)


On 10/20/2016 08:02 PM, Miguel Dias Costa wrote:

Dear Jack,

I sometimes use --dump-env-script [1] (on the .eb files, not
the -devel files)

Miguel

[1] https://github.com/hpcugent/easybuild-framework/pull/1624



On 21/10/16 08:46, Jack Perdue wrote:

Howdy EB gods (Ken and crew),

So EB, puts some useful environment settings in
//easybuild/*-devel

Is there a way to utilize those variables when not
using EB?

For example, I assume that if a user loads icc that they
more than likely would like CC=icc (CFLAGS is a different
matter).

But EB doesn't do that now (probably for good reason).

But it WOULD be nice if I could somehow use the variables in
the -devel file (in bash) without all the extraneous stuff.

EB has a rich collection of useful environment variables
(especially when using Intel toolchains ala
FFTW/LAPACK/BLAS)
how can we make them available to the user (who just wants to
compile against EB modules without using EB).






Forschungszentrum Juelich GmbH
52425 Juelich
Sitz der Gesellschaft: Juelich
Eingetragen im Handelsregister des Amtsgerichts Dueren Nr. HR B 3498
Vorsitzender des Aufsichtsrats: MinDir Dr. Karl Eugen Huthmacher
Geschaeftsfuehrung: Prof. Dr.-Ing. Wolfgang Marquardt (Vorsitzender),
Karsten Beneke (stellv. Vorsitzender), Prof. Dr.-Ing. Harald Bolt,
Prof. Dr. Sebastian M. Schmidt

Re: [easybuild] easybuild -devel files for users?

[Miguel Dias Costa]

that looks even better, good to know!

On 21/10/16 12:25, Alan O'Cais wrote:


There's also an easyblock to create a module filled with the 
environment variables used by a tool chain during the build process, 
an example use is at

https://github.com/hpcugent/easybuild-easyconfigs/tree/master/easybuild/easyconfigs/b/buildenv


On 21 Oct 2016 3:10 a.m., "Jack Perdue" > wrote:


Howdy Miguel,

I totally missed that in some release notes along the way.
That's awesome.  Thanks! (to Miguel and all those that made
it possible)

jack (seeing it of great use to our users)


On 10/20/2016 08:02 PM, Miguel Dias Costa wrote:

Dear Jack,

I sometimes use --dump-env-script [1] (on the .eb files, not
the -devel files)

Miguel

[1] https://github.com/hpcugent/easybuild-framework/pull/1624



On 21/10/16 08:46, Jack Perdue wrote:

Howdy EB gods (Ken and crew),

So EB, puts some useful environment settings in
//easybuild/*-devel

Is there a way to utilize those variables when not
using EB?

For example, I assume that if a user loads icc that they
more than likely would like CC=icc (CFLAGS is a different
matter).

But EB doesn't do that now (probably for good reason).

But it WOULD be nice if I could somehow use the variables in
the -devel file (in bash) without all the extraneous stuff.

EB has a rich collection of useful environment variables
(especially when using Intel toolchains ala
FFTW/LAPACK/BLAS)
how can we make them available to the user (who just wants to
compile against EB modules without using EB).






Forschungszentrum Juelich GmbH
52425 Juelich
Sitz der Gesellschaft: Juelich
Eingetragen im Handelsregister des Amtsgerichts Dueren Nr. HR B 3498
Vorsitzender des Aufsichtsrats: MinDir Dr. Karl Eugen Huthmacher
Geschaeftsfuehrung: Prof. Dr.-Ing. Wolfgang Marquardt (Vorsitzender),
Karsten Beneke (stellv. Vorsitzender), Prof. Dr.-Ing. Harald Bolt,
Prof. Dr. Sebastian M. Schmidt

Re: [easybuild] easybuild -devel files for users?

[Alan O'Cais]

There's also an easyblock to create a module filled with the environment 
variables used by a tool chain during the build process, an example use is at
https://github.com/hpcugent/easybuild-easyconfigs/tree/master/easybuild/easyconfigs/b/buildenv

On 21 Oct 2016 3:10 a.m., "Jack Perdue" 
mailto:j-per...@tamu.edu>> wrote:
Howdy Miguel,

I totally missed that in some release notes along the way.
That's awesome.  Thanks! (to Miguel and all those that made
it possible)

jack (seeing it of great use to our users)


On 10/20/2016 08:02 PM, Miguel Dias Costa wrote:
Dear Jack,

I sometimes use --dump-env-script [1] (on the .eb files, not the -devel files)

Miguel

[1] https://github.com/hpcugent/easybuild-framework/pull/1624


On 21/10/16 08:46, Jack Perdue wrote:
Howdy EB gods (Ken and crew),

So EB, puts some useful environment settings in
//easybuild/*-devel

Is there a way to utilize those variables when not
using EB?

For example, I assume that if a user loads icc that they
more than likely would like CC=icc (CFLAGS is a different
matter).

But EB doesn't do that now (probably for good reason).

But it WOULD be nice if I could somehow use the variables in
the -devel file (in bash) without all the extraneous stuff.

EB has a rich collection of useful environment variables
(especially when using Intel toolchains ala FFTW/LAPACK/BLAS)
how can we make them available to the user (who just wants to
compile against EB modules without using EB).






Forschungszentrum Juelich GmbH
52425 Juelich
Sitz der Gesellschaft: Juelich
Eingetragen im Handelsregister des Amtsgerichts Dueren Nr. HR B 3498
Vorsitzender des Aufsichtsrats: MinDir Dr. Karl Eugen Huthmacher
Geschaeftsfuehrung: Prof. Dr.-Ing. Wolfgang Marquardt (Vorsitzender),
Karsten Beneke (stellv. Vorsitzender), Prof. Dr.-Ing. Harald Bolt,
Prof. Dr. Sebastian M. Schmidt

Re: [easybuild] easybuild -devel files for users?

[Jack Perdue]

Howdy Miguel,

I totally missed that in some release notes along the way.
That's awesome.  Thanks! (to Miguel and all those that made
it possible)

jack (seeing it of great use to our users)


On 10/20/2016 08:02 PM, Miguel Dias Costa wrote:

Dear Jack,

I sometimes use --dump-env-script [1] (on the .eb files, not the 
-devel files)


Miguel

[1] https://github.com/hpcugent/easybuild-framework/pull/1624


On 21/10/16 08:46, Jack Perdue wrote:

Howdy EB gods (Ken and crew),

So EB, puts some useful environment settings in
//easybuild/*-devel

Is there a way to utilize those variables when not
using EB?

For example, I assume that if a user loads icc that they
more than likely would like CC=icc (CFLAGS is a different
matter).

But EB doesn't do that now (probably for good reason).

But it WOULD be nice if I could somehow use the variables in
the -devel file (in bash) without all the extraneous stuff.

EB has a rich collection of useful environment variables
(especially when using Intel toolchains ala FFTW/LAPACK/BLAS)
how can we make them available to the user (who just wants to
compile against EB modules without using EB).

Re: [easybuild] easybuild -devel files for users?

[Miguel Dias Costa]

Dear Jack,

I sometimes use --dump-env-script [1] (on the .eb files, not the -devel 
files)


Miguel

[1] https://github.com/hpcugent/easybuild-framework/pull/1624


On 21/10/16 08:46, Jack Perdue wrote:

Howdy EB gods (Ken and crew),

So EB, puts some useful environment settings in
//easybuild/*-devel

Is there a way to utilize those variables when not
using EB?

For example, I assume that if a user loads icc that they
more than likely would like CC=icc (CFLAGS is a different
matter).

But EB doesn't do that now (probably for good reason).

But it WOULD be nice if I could somehow use the variables in
the -devel file (in bash) without all the extraneous stuff.

EB has a rich collection of useful environment variables
(especially when using Intel toolchains ala FFTW/LAPACK/BLAS)
how can we make them available to the user (who just wants to
compile against EB modules without using EB).


--
Dias Costa, Miguel (Dr)
HPC Architect
Centre for Advanced 2D Materials
National University of Singapore

[easybuild] easybuild -devel files for users?

[Jack Perdue]

Howdy EB gods (Ken and crew),

So EB, puts some useful environment settings in
//easybuild/*-devel

Is there a way to utilize those variables when not
using EB?

For example, I assume that if a user loads icc that they
more than likely would like CC=icc (CFLAGS is a different
matter).

But EB doesn't do that now (probably for good reason).

But it WOULD be nice if I could somehow use the variables in
the -devel file (in bash) without all the extraneous stuff.

EB has a rich collection of useful environment variables
(especially when using Intel toolchains ala FFTW/LAPACK/BLAS)
how can we make them available to the user (who just wants to
compile against EB modules without using EB).

--
Jack Perdue
Lead Systems Administrator
High Performance Research Computing
TAMU Division of Research
j-per...@tamu.eduhttp://hprc.tamu.edu
HPRC Helpdesk: h...@hprc.tamu.edu