hi fotis,
On 05/07/2012 15:45, Kenneth Hoste wrote:
EasyBuild v0.8 has just been released via github.
Overall it works well, thanks for the release. Some notes:
(1)
Building eg. latest gcc compiler v4.7.1 was a breeze. :-)
I come to realize that the "goalf" stack is a heavy dependency:
Can we relax the dependency between Python & GCC? Is it really needed?
what do you mean with this?
in principle you should not load the submodules of the toolkit. if you
want GCC, just load the goalf module, or better yet, just load Python.
there is no easy way here: eg the Python install (unless i'm mistaken)
comes with mpi4py, so you need a mpi stack, and numpy needs blas and
fft(w). what is currently in a toolkit is "minimal" build environment
simply put if you want GCC, look for a toolkit which name start with g ;)
hope this makes things clearer.
stijn
fgeorgatos@d-cluster1-1:~$ module purge
fgeorgatos@d-cluster1-1:~$ module list
No Modulefiles Currently Loaded.
fgeorgatos@d-cluster1-1:~$ module load GCC/4.7.1 # conflicts with next one
fgeorgatos@d-cluster1-1:~$ module load Python/3.2.3-goalf-1.1.0-no-OFED
GCC/4.6.3(12):ERROR:150: Module 'GCC/4.6.3' conflicts with the currently
loaded module(s) 'GCC/4.7.1'
GCC/4.6.3(12):ERROR:102: Tcl command execution failed: conflict GCC
GCC/4.6.3(12):ERROR:150: Module 'GCC/4.6.3' conflicts with the currently
loaded module(s) 'GCC/4.7.1'
GCC/4.6.3(12):ERROR:102: Tcl command execution failed: conflict GCC
GCC/4.6.3(12):ERROR:150: Module 'GCC/4.6.3' conflicts with the currently
loaded module(s) 'GCC/4.7.1'
GCC/4.6.3(12):ERROR:102: Tcl command execution failed: conflict GCC
GCC/4.6.3(12):ERROR:150: Module 'GCC/4.6.3' conflicts with the currently
loaded module(s) 'GCC/4.7.1'
GCC/4.6.3(12):ERROR:102: Tcl command execution failed: conflict GCC
GCC/4.6.3(12):ERROR:150: Module 'GCC/4.6.3' conflicts with the currently
loaded module(s) 'GCC/4.7.1'
GCC/4.6.3(12):ERROR:102: Tcl command execution failed: conflict GCC
GCC/4.6.3(12):ERROR:150: Module 'GCC/4.6.3' conflicts with the currently
loaded module(s) 'GCC/4.7.1'
GCC/4.6.3(12):ERROR:102: Tcl command execution failed: conflict GCC
GCC/4.6.3(12):ERROR:150: Module 'GCC/4.6.3' conflicts with the currently
loaded module(s) 'GCC/4.7.1'
GCC/4.6.3(12):ERROR:102: Tcl command execution failed: conflict GCC
fgeorgatos@d-cluster1-1:~$
(2)
A minor typo with Libint libs is visible here:
$ cat *err|grep -1 URL
ERROR: Failed to process easyconfig
/home/clusterusers/fgeorgatos/arena/easybuild/easybuild/easyconfigs/l/Libint/Libint-goalf-1.1.0-no-OFED.eb:
EasyBuild crashed with an error (at easybuild/framework/application.py:393 in
process_ebfile): Don't you mean 'sourceURLs' instead of 'sourceURLS' as eb
file variable.
ERROR: Failed to process easyconfig
/home/clusterusers/fgeorgatos/arena/easybuild/easybuild/easyconfigs/l/Libint/Libint-ictce-4.0.6.eb:
EasyBuild crashed with an error (at easybuild/framework/application.py:393 in
process_ebfile): Don't you mean 'sourceURLs' instead of 'sourceURLS' as eb
file variable.
(3)
This release adds support for building Maple, MrBayes, NCL, WRF, WPS, and all
their dependencies ( BEAGLE, [...]
The MrBayes-BEAGLE dependency seems to break with the following error:
$ cat OAR.142017.stdout # these builds are by now regular cluster jobs
== resolving dependencies ...
== processing EasyBuild easyconfig
/mnt/nfs/users/homedirs/fgeorgatos/arena/easybuild/easybuild/easyconfigs/b/BEAGLE/BEAGLE-20120124-goalf-1.1.0-no-OFED.eb
== preparing...
== unpacking...
== configuring...
== FAILED: Installation ended unsuccessfully (build directory:
/home/clusterusers/fgeorgatos/easybuild_build/BEAGLE/20120124/goalf-1.1.0-no-OFED/goalf-1.1.0-no-OFED):
autoBuild Failed (last 300 chars): EasyBuild crashed with an error (at
easybuild/tools/filetools.py:310 in run_cmd): run_cmd " ./configure
--prefix=/home/clusterusers/fgeorgatos/easybuild/software/BEAGLE/20120124-goalf-1.1.0-no-OFED
" exited with exitcode 127 and output:
/bin/bash: ./configure: No such file or directory
==
WARNING: Build exited with exit code 1. 0 possible error(s) were detected in
the build logs, please verify the build.
== Results of the build can be found in the log file
/tmp/easybuild-BEAGLE-20120124-20120710.183802.log
(because /tmp is local per node, the info is "lost" somewhere in the system;
I did dig it though and, the error has as reported above; a dir name issue??)
tia,
Fotis
