Re: [easybuild] Automatic detection of hidden modules

[Vanzo, Davide]

Markus,
you are absolutely right.
The only way to do what I want is the following:

$ eb GCC-5.4.0-2.26.eb -D --hide-deps=M4,Bison,flex,zlib,binutils,GCCcore 
--hide-toolchains=GCCcore

or to specify the dependencies that need to be hidden in the 
EASYBUILD_HIDE_DEPS environment variable.
I think that at the moment it is good enough for me.

DV


On Oct 18 2016, at 12:41 pm, Markus Geimer  wrote:

Alan, Davide,

> hidden = True is now supported within EB (see
> https://github.com/hpcugent/easybuild-framework/pull/1837), just add
> that to your GCCcore eb file

Since GCCcore is a toolchain, '--hide-deps' or 'hidden = True' alone
doesn't help. 'hidden = True' only applies to the installation itself,
but not necessarily when the package is used as a dependency (see
below). And '--hide-deps' only applies if GCCcore is used as a
dependency, but not when used as a toolchain. Therefore, EB 2.9.0
also supports a '--hide-toolchains' option, which should help in this
case. (Note that GCCcore needs to be marked as hidden in both ways.)

> If so, is there any chance we will see such feature (maybe not by
> default but as an eb option flag) in the future?
>
> If not, what would you suggest? Obviously I could manually edit all
> easyconfig files by adding the hiddendependencies but that may be
> quite annoying in the long term.

If you list your easyconfig archive and/or "golden repo" before the
easyconfig dir of your EB install in robot path, EasyBuild will look
at those first and correctly handles packages including 'hidden=True'
even w/o listing them in hiddendependencies. However, for other
robot-path setups, an 'automatically consider hidden modules' feature
is still missing in EasyBuild. Let me use Kenneth's favorite in such
cases: "It should not be too hard to implement this..." ;-)

Markus

--
Dr. Markus Geimer
Juelich Supercomputing Centre
Institute for Advanced Simulation
Forschungszentrum Juelich GmbH
52425 Juelich, Germany

Phone: +49-2461-61-1773
Fax: +49-2461-61-6656
E-Mail: m.gei...@fz-juelich.de
Web: http://www.fz-juelich.de/jsc



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] Automatic detection of hidden modules

[Vanzo, Davide]

Great! Thank you guys.

DV

On Oct 18 2016, at 12:36 pm, Bart Oldeman  wrote:
Also you can put that list in a configuration file, e.g. I have a config.cfg 
file with
hide-deps = icc,ifort
and use
EASYBUILD_CONFIGFILES
to point to that file. That is good for the environment.

On 18 October 2016 at 13:26, Alan O'Cais 
> wrote:
hidden = True
is now supported within EB (see 
https://github.com/hpcugent/easybuild-framework/pull/1837), just add that to 
your GCCcore eb file

We have a long list of software packages hidden by default, this is the setting 
you also might suit you:
-bash-4.2$ echo $EASYBUILD_HIDE_DEPS
ANTLR,APR,APR-util,AT-SPI2-ATK,AT-SPI2-core,ATK,Autoconf,Automake,Bison,CUSP,Coreutils,DB,DBus,DocBook-XML,Dyninst,ETSF_IO,FFmpeg,FLTK,FTGL,GCCcore,GDAL,GL2PS,GLEW,GLib,GLPK,GPC,GObject-Introspection,GTI,GTK+,GTS,Gdk-Pixbuf,Ghostscript,GraphicsMagick,GtkSourceView,HarfBuzz,JUnit,JasPer,LibTIFF,LibUUID,Libint,M4,Mesa,NASM,OPARI2,OTF2,PCRE,PDT,PROJ,Pango,PnMPI,PyCairo,PyGObject,PyQt,Qhull,Qt,Qt5,S-Lang,SCons,SIP,SQLite,SWIG,Serf,Szip,Tcl,Tk,UDUNITS,XML-Parser,XZ,XKeyboardConfig,YAXT,Yasm,adwaita-icon-theme,ant,assimp,binutils,byacc,bzip2,cairo,dbus-glib,damageproto,eudev,expat,g2clib,g2lib,gc,glproto,gperf,guile,grib_api,gsettings-desktop-schemas,fixesproto,fontsproto,fontconfig,freeglut,freetype,gettext,icc,ifort,inputproto,intltool,itstool,jhbuild,kbproto,libGLU,libICE,libSM,libX11,libXau,libXaw,libXcursor,libXdamage,libXdmcp,libXext,libXfixes,libXfont,libXft,libXi,libXinerama,libXmu,libXpm,libXrandr,libXrender,libXt,libXtst,libcerf,libcroco,libctl,libdap,libdrm,libdwarf,libelf,libevent,libffi,libfontenc,libgd,libgeotiff,libglade,libidn,libjpeg-turbo,libmatheval,libpng,libpciaccess,libpthread-stubs,libreadline,librsvg,libtool,libunistring,libunwind,libyaml,libxcb,libxkbcommon,libxml2,libxslt,makedepend,motif,ncurses,pixman,pkg-config,pkgconfig,popt,pscom,qrupdate,randrproto,recordproto,renderproto,scrollkeeper,texinfo,util-linux,wxPropertyGrid,wxWidgets,x264,xbitmaps,xcb-proto,xcb-util,xcb-util-image,xcb-util-keysyms,xcb-util-renderutil,xcb-util-wm,xextproto,xineramaproto,xorg-macros,xprop,xproto,xtrans,zlib



On 18 October 2016 at 18:18, Vanzo, Davide 
> wrote:
Hello,
Although we wold love to use EB in production there is still one thing that 
stops us from doing so. Since we need to keep the modules list in Lmod as clean 
as possible it is essential for us to be able to tell EB to automatically look 
for dependencies within hidden modules even if not explicitly listed as 
hiddendependencies in the easyconfig files. Let me show you with the case I am 
struggling with.

I want to install GCC but keep the GCCcore module hidden. As you can see from 
the output below if I ask to hide GCCcore it gets built twice and two modules 
get generated: one hidden and one visible. My understanding is that it happens 
because when rebuilding all dependencies with GCCcore (instead of the system 
GCC) they don't have GCCcore within a hiddendependencies list and since EB does 
not automatically scan for hidden modules it builds GCCcore again. Am I right?

If so, is there any chance we will see such feature (maybe not by default but 
as an eb option flag) in the future?

If not, what would you suggest? Obviously I could manually edit all easyconfig 
files by adding the hiddendependencies but that may be quite annoying in the 
long term.

In addition, what do you think about being able to specify the "hide-deps" list 
directly into the easyconfig?

Thanks!


$ eb GCC-5.4.0-2.26.eb -D --hide-deps=M4,Bison,flex,zlib,binutils,GCCcore
== temporary log file in case of crash /tmp/eb-bLnY30/easybuild-wrqlUH.log
Dry run: printing build status of easyconfigs and dependencies
CFGS=/opt/easybuild/software/EasyBuild/2.9.0/lib/python2.7/site-packages/easybuild_easyconfigs-2.9.0-py2.7.egg/easybuild/easyconfigs
* [ ] $CFGS/m/M4/M4-1.4.17.eb (module: Core | M4/.1.4.17)
* [ ] $CFGS/b/Bison/Bison-3.0.4.eb (module: Core | Bison/.3.0.4)
* [ ] $CFGS/f/flex/flex-2.6.0.eb (module: Core | flex/.2.6.0)
* [ ] $CFGS/z/zlib/zlib-1.2.8.eb (module: Core | zlib/.1.2.8)
* [ ] $CFGS/b/binutils/binutils-2.26.eb (module: Core | binutils/.2.26)
* [ ] $CFGS/g/GCCcore/GCCcore-5.4.0.eb (module: Core | GCCcore/.5.4.0)
* [ ] $CFGS/g/GCCcore/GCCcore-5.4.0.eb (module: Core | GCCcore/5.4.0)
* [ ] $CFGS/z/zlib/zlib-1.2.8-GCCcore-5.4.0.eb (module: Compiler/GCCcore/5.4.0 
| zlib/.1.2.8)
* [ ] $CFGS/m/M4/M4-1.4.17-GCCcore-5.4.0.eb (module: Compiler/GCCcore/5.4.0 | 
M4/.1.4.17)
* [ ] $CFGS/b/Bison/Bison-3.0.4-GCCcore-5.4.0.eb (module: 
Compiler/GCCcore/5.4.0 | Bison/.3.0.4)
* [ ] $CFGS/f/flex/flex-2.6.0-GCCcore-5.4.0.eb (module: Compiler/GCCcore/5.4.0 
| flex/.2.6.0)
* [ ] $CFGS/b/binutils/binutils-2.26-GCCcore-5.4.0.eb (module: 
Compiler/GCCcore/5.4.0 | binutils/.2.26)
* [ ] $CFGS/g/GCC/GCC-5.4.0-2.26.eb (module: Core | 

Re: [easybuild] Automatic detection of hidden modules

[Bart Oldeman]

Also you can put that list in a configuration file, e.g. I have a
config.cfg file with
hide-deps = icc,ifort
and use
EASYBUILD_CONFIGFILES
to point to that file. That is good for the environment.

On 18 October 2016 at 13:26, Alan O'Cais  wrote:

> hidden = True
> is now supported within EB (see https://github.com/hpcugent/
> easybuild-framework/pull/1837), just add that to your GCCcore eb file
>
> We have a long list of software packages hidden by default, this is the
> setting you also might suit you:
> -bash-4.2$ echo $EASYBUILD_HIDE_DEPS
> ANTLR,APR,APR-util,AT-SPI2-ATK,AT-SPI2-core,ATK,Autoconf,
> Automake,Bison,CUSP,Coreutils,DB,DBus,DocBook-XML,Dyninst,
> ETSF_IO,FFmpeg,FLTK,FTGL,GCCcore,GDAL,GL2PS,GLEW,GLib,GLPK,GPC,GObject-
> Introspection,GTI,GTK+,GTS,Gdk-Pixbuf,Ghostscript,
> GraphicsMagick,GtkSourceView,HarfBuzz,JUnit,JasPer,LibTIFF,
> LibUUID,Libint,M4,Mesa,NASM,OPARI2,OTF2,PCRE,PDT,PROJ,
> Pango,PnMPI,PyCairo,PyGObject,PyQt,Qhull,Qt,Qt5,S-Lang,
> SCons,SIP,SQLite,SWIG,Serf,Szip,Tcl,Tk,UDUNITS,XML-
> Parser,XZ,XKeyboardConfig,YAXT,Yasm,adwaita-icon-theme,
> ant,assimp,binutils,byacc,bzip2,cairo,dbus-glib,damageproto,eudev,expat,
> g2clib,g2lib,gc,glproto,gperf,guile,grib_api,gsettings-
> desktop-schemas,fixesproto,fontsproto,fontconfig,
> freeglut,freetype,gettext,icc,ifort,inputproto,intltool,
> itstool,jhbuild,kbproto,libGLU,libICE,libSM,libX11,
> libXau,libXaw,libXcursor,libXdamage,libXdmcp,libXext,
> libXfixes,libXfont,libXft,libXi,libXinerama,libXmu,
> libXpm,libXrandr,libXrender,libXt,libXtst,libcerf,
> libcroco,libctl,libdap,libdrm,libdwarf,libelf,libevent,
> libffi,libfontenc,libgd,libgeotiff,libglade,libidn,
> libjpeg-turbo,libmatheval,libpng,libpciaccess,
> libpthread-stubs,libreadline,librsvg,libtool,libunistring,
> libunwind,libyaml,libxcb,libxkbcommon,libxml2,libxslt,
> makedepend,motif,ncurses,pixman,pkg-config,pkgconfig,popt,pscom,qrupdate,
> randrproto,recordproto,renderproto,scrollkeeper,texinfo,util-linux,
> wxPropertyGrid,wxWidgets,x264,xbitmaps,xcb-proto,xcb-util,
> xcb-util-image,xcb-util-keysyms,xcb-util-renderutil,xcb-util-wm,xextproto,
> xineramaproto,xorg-macros,xprop,xproto,xtrans,zlib
>
>
>
> On 18 October 2016 at 18:18, Vanzo, Davide 
> wrote:
>
>> Hello,
>> Although we wold love to use EB in production there is still one thing
>> that stops us from doing so. Since we need to keep the modules list in
>> Lmod as clean as possible it is essential for us to be able to tell EB to
>> automatically look for dependencies within hidden modules even if not
>> explicitly listed as hiddendependencies in the easyconfig files. Let me
>> show you with the case I am struggling with.
>>
>> I want to install GCC but keep the GCCcore module hidden. As you can see
>> from the output below if I ask to hide GCCcore it gets built twice and two
>> modules get generated: one hidden and one visible. My understanding is that
>> it happens because when rebuilding all dependencies with GCCcore (instead
>> of the system GCC) they don't have GCCcore within a hiddendependencies list
>> and since EB does not automatically scan for hidden modules it builds
>> GCCcore again. Am I right?
>>
>> If so, is there any chance we will see such feature (maybe not by default
>> but as an eb option flag) in the future?
>>
>> If not, what would you suggest? Obviously I could manually edit all
>> easyconfig files by adding the hiddendependencies but that may be quite
>> annoying in the long term.
>>
>> In addition, what do you think about being able to specify the
>> "hide-deps" list directly into the easyconfig?
>>
>> Thanks!
>>
>>
>> $ eb GCC-5.4.0-2.26.eb -D --hide-deps=M4,Bison,flex,zlib,binutils,GCCcore
>> == temporary log file in case of crash /tmp/eb-bLnY30/easybuild-wrqlU
>> H.log
>> Dry run: printing build status of easyconfigs and dependencies
>> CFGS=/opt/easybuild/software/EasyBuild/2.9.0/lib/python2.7/s
>> ite-packages/easybuild_easyconfigs-2.9.0-py2.7.egg/easybuild/easyconfigs
>> * [ ] $CFGS/m/M4/M4-1.4.17.eb (module: Core | M4/.1.4.17)
>> * [ ] $CFGS/b/Bison/Bison-3.0.4.eb (module: Core | Bison/.3.0.4)
>> * [ ] $CFGS/f/flex/flex-2.6.0.eb (module: Core | flex/.2.6.0)
>> * [ ] $CFGS/z/zlib/zlib-1.2.8.eb (module: Core | zlib/.1.2.8)
>> * [ ] $CFGS/b/binutils/binutils-2.26.eb (module: Core | binutils/.2.26)
>> * [ ] $CFGS/g/GCCcore/GCCcore-5.4.0.eb (module: Core | GCCcore/.5.4.0)
>> * [ ] $CFGS/g/GCCcore/GCCcore-5.4.0.eb (module: Core | GCCcore/5.4.0)
>> * [ ] $CFGS/z/zlib/zlib-1.2.8-GCCcore-5.4.0.eb (module:
>> Compiler/GCCcore/5.4.0 | zlib/.1.2.8)
>> * [ ] $CFGS/m/M4/M4-1.4.17-GCCcore-5.4.0.eb (module:
>> Compiler/GCCcore/5.4.0 | M4/.1.4.17)
>> * [ ] $CFGS/b/Bison/Bison-3.0.4-GCCcore-5.4.0.eb (module:
>> Compiler/GCCcore/5.4.0 | Bison/.3.0.4)
>> * [ ] $CFGS/f/flex/flex-2.6.0-GCCcore-5.4.0.eb (module:
>> Compiler/GCCcore/5.4.0 | flex/.2.6.0)
>> * [ ] $CFGS/b/binutils/binutils-2.26-GCCcore-5.4.0.eb (module:
>> Compiler/GCCcore/5.4.0 | 

Re: [easybuild] Automatic detection of hidden modules

[Alan O'Cais]

hidden = True
is now supported within EB (see 
https://github.com/hpcugent/easybuild-framework/pull/1837), just add that to 
your GCCcore eb file

We have a long list of software packages hidden by default, this is the setting 
you also might suit you:
-bash-4.2$ echo $EASYBUILD_HIDE_DEPS
ANTLR,APR,APR-util,AT-SPI2-ATK,AT-SPI2-core,ATK,Autoconf,Automake,Bison,CUSP,Coreutils,DB,DBus,DocBook-XML,Dyninst,ETSF_IO,FFmpeg,FLTK,FTGL,GCCcore,GDAL,GL2PS,GLEW,GLib,GLPK,GPC,GObject-Introspection,GTI,GTK+,GTS,Gdk-Pixbuf,Ghostscript,GraphicsMagick,GtkSourceView,HarfBuzz,JUnit,JasPer,LibTIFF,LibUUID,Libint,M4,Mesa,NASM,OPARI2,OTF2,PCRE,PDT,PROJ,Pango,PnMPI,PyCairo,PyGObject,PyQt,Qhull,Qt,Qt5,S-Lang,SCons,SIP,SQLite,SWIG,Serf,Szip,Tcl,Tk,UDUNITS,XML-Parser,XZ,XKeyboardConfig,YAXT,Yasm,adwaita-icon-theme,ant,assimp,binutils,byacc,bzip2,cairo,dbus-glib,damageproto,eudev,expat,g2clib,g2lib,gc,glproto,gperf,guile,grib_api,gsettings-desktop-schemas,fixesproto,fontsproto,fontconfig,freeglut,freetype,gettext,icc,ifort,inputproto,intltool,itstool,jhbuild,kbproto,libGLU,libICE,libSM,libX11,libXau,libXaw,libXcursor,libXdamage,libXdmcp,libXext,libXfixes,libXfont,libXft,libXi,libXinerama,libXmu,libXpm,libXrandr,libXrender,libXt,libXtst,libcerf,libcroco,libctl,libdap,libdrm,libdwarf,libelf,libevent,libffi,libfontenc,libgd,libgeotiff,libglade,libidn,libjpeg-turbo,libmatheval,libpng,libpciaccess,libpthread-stubs,libreadline,librsvg,libtool,libunistring,libunwind,libyaml,libxcb,libxkbcommon,libxml2,libxslt,makedepend,motif,ncurses,pixman,pkg-config,pkgconfig,popt,pscom,qrupdate,randrproto,recordproto,renderproto,scrollkeeper,texinfo,util-linux,wxPropertyGrid,wxWidgets,x264,xbitmaps,xcb-proto,xcb-util,xcb-util-image,xcb-util-keysyms,xcb-util-renderutil,xcb-util-wm,xextproto,xineramaproto,xorg-macros,xprop,xproto,xtrans,zlib



On 18 October 2016 at 18:18, Vanzo, Davide 
> wrote:
Hello,
Although we wold love to use EB in production there is still one thing that 
stops us from doing so. Since we need to keep the modules list in Lmod as clean 
as possible it is essential for us to be able to tell EB to automatically look 
for dependencies within hidden modules even if not explicitly listed as 
hiddendependencies in the easyconfig files. Let me show you with the case I am 
struggling with.

I want to install GCC but keep the GCCcore module hidden. As you can see from 
the output below if I ask to hide GCCcore it gets built twice and two modules 
get generated: one hidden and one visible. My understanding is that it happens 
because when rebuilding all dependencies with GCCcore (instead of the system 
GCC) they don't have GCCcore within a hiddendependencies list and since EB does 
not automatically scan for hidden modules it builds GCCcore again. Am I right?

If so, is there any chance we will see such feature (maybe not by default but 
as an eb option flag) in the future?

If not, what would you suggest? Obviously I could manually edit all easyconfig 
files by adding the hiddendependencies but that may be quite annoying in the 
long term.

In addition, what do you think about being able to specify the "hide-deps" list 
directly into the easyconfig?

Thanks!


$ eb GCC-5.4.0-2.26.eb -D --hide-deps=M4,Bison,flex,zlib,binutils,GCCcore
== temporary log file in case of crash /tmp/eb-bLnY30/easybuild-wrqlUH.log
Dry run: printing build status of easyconfigs and dependencies
CFGS=/opt/easybuild/software/EasyBuild/2.9.0/lib/python2.7/site-packages/easybuild_easyconfigs-2.9.0-py2.7.egg/easybuild/easyconfigs
* [ ] $CFGS/m/M4/M4-1.4.17.eb (module: Core | M4/.1.4.17)
* [ ] $CFGS/b/Bison/Bison-3.0.4.eb (module: Core | Bison/.3.0.4)
* [ ] $CFGS/f/flex/flex-2.6.0.eb (module: Core | flex/.2.6.0)
* [ ] $CFGS/z/zlib/zlib-1.2.8.eb (module: Core | zlib/.1.2.8)
* [ ] $CFGS/b/binutils/binutils-2.26.eb (module: Core | binutils/.2.26)
* [ ] $CFGS/g/GCCcore/GCCcore-5.4.0.eb (module: Core | GCCcore/.5.4.0)
* [ ] $CFGS/g/GCCcore/GCCcore-5.4.0.eb (module: Core | GCCcore/5.4.0)
* [ ] $CFGS/z/zlib/zlib-1.2.8-GCCcore-5.4.0.eb (module: Compiler/GCCcore/5.4.0 
| zlib/.1.2.8)
* [ ] $CFGS/m/M4/M4-1.4.17-GCCcore-5.4.0.eb (module: Compiler/GCCcore/5.4.0 | 
M4/.1.4.17)
* [ ] $CFGS/b/Bison/Bison-3.0.4-GCCcore-5.4.0.eb (module: 
Compiler/GCCcore/5.4.0 | Bison/.3.0.4)
* [ ] $CFGS/f/flex/flex-2.6.0-GCCcore-5.4.0.eb (module: Compiler/GCCcore/5.4.0 
| flex/.2.6.0)
* [ ] $CFGS/b/binutils/binutils-2.26-GCCcore-5.4.0.eb (module: 
Compiler/GCCcore/5.4.0 | binutils/.2.26)
* [ ] $CFGS/g/GCC/GCC-5.4.0-2.26.eb (module: Core | GCC/5.4.0-2.26)
== Temporary log file(s) /tmp/eb-bLnY30/easybuild-wrqlUH.log* have been removed.
== Temporary directory /tmp/eb-bLnY30 has been removed.


--
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

[easybuild] Automatic detection of hidden modules

[Vanzo, Davide]

Hello,
Although we wold love to use EB in production there is still one thing that 
stops us from doing so. Since we need to keep the modules list in Lmod as clean 
as possible it is essential for us to be able to tell EB to automatically look 
for dependencies within hidden modules even if not explicitly listed as 
hiddendependencies in the easyconfig files. Let me show you with the case I am 
struggling with.

I want to install GCC but keep the GCCcore module hidden. As you can see from 
the output below if I ask to hide GCCcore it gets built twice and two modules 
get generated: one hidden and one visible. My understanding is that it happens 
because when rebuilding all dependencies with GCCcore (instead of the system 
GCC) they don't have GCCcore within a hiddendependencies list and since EB does 
not automatically scan for hidden modules it builds GCCcore again. Am I right?

If so, is there any chance we will see such feature (maybe not by default but 
as an eb option flag) in the future?

If not, what would you suggest? Obviously I could manually edit all easyconfig 
files by adding the hiddendependencies but that may be quite annoying in the 
long term.

In addition, what do you think about being able to specify the "hide-deps" list 
directly into the easyconfig?

Thanks!


$ eb GCC-5.4.0-2.26.eb -D --hide-deps=M4,Bison,flex,zlib,binutils,GCCcore
== temporary log file in case of crash /tmp/eb-bLnY30/easybuild-wrqlUH.log
Dry run: printing build status of easyconfigs and dependencies
CFGS=/opt/easybuild/software/EasyBuild/2.9.0/lib/python2.7/site-packages/easybuild_easyconfigs-2.9.0-py2.7.egg/easybuild/easyconfigs
* [ ] $CFGS/m/M4/M4-1.4.17.eb (module: Core | M4/.1.4.17)
* [ ] $CFGS/b/Bison/Bison-3.0.4.eb (module: Core | Bison/.3.0.4)
* [ ] $CFGS/f/flex/flex-2.6.0.eb (module: Core | flex/.2.6.0)
* [ ] $CFGS/z/zlib/zlib-1.2.8.eb (module: Core | zlib/.1.2.8)
* [ ] $CFGS/b/binutils/binutils-2.26.eb (module: Core | binutils/.2.26)
* [ ] $CFGS/g/GCCcore/GCCcore-5.4.0.eb (module: Core | GCCcore/.5.4.0)
* [ ] $CFGS/g/GCCcore/GCCcore-5.4.0.eb (module: Core | GCCcore/5.4.0)
* [ ] $CFGS/z/zlib/zlib-1.2.8-GCCcore-5.4.0.eb (module: Compiler/GCCcore/5.4.0 
| zlib/.1.2.8)
* [ ] $CFGS/m/M4/M4-1.4.17-GCCcore-5.4.0.eb (module: Compiler/GCCcore/5.4.0 | 
M4/.1.4.17)
* [ ] $CFGS/b/Bison/Bison-3.0.4-GCCcore-5.4.0.eb (module: 
Compiler/GCCcore/5.4.0 | Bison/.3.0.4)
* [ ] $CFGS/f/flex/flex-2.6.0-GCCcore-5.4.0.eb (module: Compiler/GCCcore/5.4.0 
| flex/.2.6.0)
* [ ] $CFGS/b/binutils/binutils-2.26-GCCcore-5.4.0.eb (module: 
Compiler/GCCcore/5.4.0 | binutils/.2.26)
* [ ] $CFGS/g/GCC/GCC-5.4.0-2.26.eb (module: Core | GCC/5.4.0-2.26)
== Temporary log file(s) /tmp/eb-bLnY30/easybuild-wrqlUH.log* have been removed.
== Temporary directory /tmp/eb-bLnY30 has been removed.


--
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