2016-09-29 11:14 GMT+02:00 Ole Holm Nielsen <[email protected]>:
> > I'm beginning to wonder if I should go back to an older foss toolchain? > > Personally I prefer to don't use the latest and greatest toolchain unless it's mandatory because the application I need to build requires it. Based on my experience this leads to hit new issues because many times you are using a compiler that the original developer never tried. Default toolchain in my cluster is goolf/1.7.20 (gcc/4.8) for historic reasons. If I had to build something from scratch right now probably I would go for foss-2015b.eb (latest foss using gcc 4.9.x). But that's a matter of taste and requirements. Regarding your question about internal documentation, what I do is to keep all my installed easyconfigs in a git repository ( http://easybuild.readthedocs.io/en/latest/Configuration.html?highlight=repositorypath#easyconfigs-repo). You can also use a local folder to store your installed easyconfigs instead of a git repo. This repo is my "documentation". If I need to reinstall something in the future I point the robot-path to my private repository of installed easyconfigs by doing "eb application-foo-bar.eb -r /path/to/my/local/repo/" regards, Pablo. > Thanks for any advice, > Ole > > > > On 09/29/2016 11:07 AM, 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. > > > > 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 > >> > > > > -- > Ole Holm Nielsen > PhD, Manager of IT services > Department of Physics, Technical University of Denmark, > Building 307, DK-2800 Kongens Lyngby, Denmark > E-mail: [email protected] > Homepage: http://dcwww.fysik.dtu.dk/~ohnielse/ > Tel: (+45) 4525 3187 / Mobile (+45) 5180 1620 > -- Pablo Escobar López HPC systems engineer sciCORE, University of Basel SIB Swiss Institute of Bioinformatics http://scicore.unibas.ch
