On 29/09/16 11:07, Ole Holm Nielsen wrote:
Pablo, Kenneth: Thanks a lot! The --try-toolchain works correctly.
Question: Is --try-toolchain just a hack for testing out something
new, or is it supposed to be used also for production modules?
If used for production, how may we remember/document the requirement
for --try-toolchain with some older easyconfig? Documentation would
seem to become an issue.
It's not really a 'hack', but it's called 'try' because there are no
guarantees that the compilation will actually work with the different
toolchain (e.g. a newer compiler version *may* be an issue, or switching
from 'foss' to 'intel' may com with surprises).
Basically, all what EasyBuild does when --try-toolchain is used is
changing the 'toolchain' line in the easyconfig file; when combined with
--robot is does this for all (missing) dependencies as well.
I'm not sure what your question is w.r.t. documentation...
Do you mean your own (internal) documentation, or the EasyBuild
documentation at http://easybuild.readthedocs.io/?
The --try-* options don't have a dedicated entry in the EasyBuild docs
yet, but they're considered stable; unless you're taking it a bit too
far, way beyond just tweaking the toolchain (version), they should work
(that is, produce 'correct' easyconfigs, there are no guarantees that
the installation will actually work).
regards,
Kenneth
Thanks,
Ole
On 09/29/2016 10:48 AM, Kenneth Hoste wrote:
Hi Ole,
On 29/09/16 10:37, Pablo Escobar Lopez wrote:
have you tried "eb Python-3.5.2-foss-2016.04.eb
--try-toolchain=foss,2016.09 -r" ?
+1 on this, the problem is that there are no easyconfigs available for
the dependencies of Python 3.5.2 with foss/2016.09.
If you combine --try-toolchain (or --try-toolchain-version) with
--robot, EasyBuild will first construct the full dependency graph using
the foss/2016.04, and then generate easyconfigs (in a temp dir) for each
of the components using foss/2016.09, and then proceed to building and
installing everything.
regards,
Kenneth
2016-09-29 8:55 GMT+02:00 Ole Holm Nielsen <[email protected]
<mailto:[email protected]>>:
I need to build Python 3.5 for the EB 2.9.0 toolchain foss-2016.09.
I copied the file Python-3.5.2-foss-2016.04.eb and replaced 04
by 09.
Unfortunately, irresolvable dependencies are found:
# eb Python-3.5.2-foss-2016.09.eb -r
== temporary log file in case of crash
/tmp/eb-mvPeVH/easybuild-tixAOo.log
== resolving dependencies ...
ERROR: Irresolvable dependencies encountered:
bzip2/1.0.6-foss-2016.09,
zlib/1.2.8-foss-2016.09, libreadline/6.3-foss-2016.09,
ncurses/6.0-foss-2016.09, SQLite/3.13.0-foss-2016.09,
Tk/8.6.5-foss-2016.09, GMP/6.1.1-foss-2016.09,
XZ/5.2.2-foss-2016.09,
libffi/3.2.1-foss-2016.09
I suppose that these dependencies could be built independently
of the
foss toolchain.
Question: Does anyone have a working EB file
Python-3.5.2-foss-2016.09.eb?
Thanks a lot,
Ole
--
Pablo Escobar López
HPC systems engineer
sciCORE, University of Basel
SIB Swiss Institute of Bioinformatics
http://scicore.unibas.ch
