One more approach: most toolchains have a corresponding zlib build. We used to fish out its ./easybuild/*devel*.eb modulefile for manual builds and for not too complex builds it could help a lot. In effect, you need to shop from something that has the same deps as what you want build and same building conditions... (the mechanical way to derive that, might imply it is a kind of feature to have)
F. Sent from my iPhone On 11 Jul 2018, at 2:56 PM, Bart Oldeman <[email protected]<mailto:[email protected]>> wrote: Note that there is also a complimentary approach using --dump-env-script, e.g.: $ eb --dump-env-script HPL-2.2-foss-2018b.eb == temporary log file in case of crash /localscratch/eb-GygDhc/easybuild-HYqbH4.log Script to set up build environment for HPL-2.2-foss-2018b.eb dumped to HPL-2.2-foss-2018b.env == Temporary log file(s) /localscratch/eb-GygDhc/easybuild-HYqbH4.log* have been removed. == Temporary directory /localscratch/eb-GygDhc has been removed. $ source HPL-2.2-foss-2018b.env $ echo $CC mpicc you can inspect the env script to see what is set. From time to time I do that when compilations are stuck: source the env script and then cd to the build folder which is still there after the compilation failed (we put it somewhere under /dev/shm for speed). Just be aware that after sourcing this the shell session is essentially "throw-away" -- it is too polluted to do much else after. Regards, Bart On Wed, 11 Jul 2018 at 08:03, Lars Viklund <[email protected]<mailto:[email protected]>> wrote: I provide them for all sorts of toolchains, preparing them with `--try-toolchain` from one of the existing ones instead of upstreaming them. They are very handy if you ever have end-user builds of software outside of EB. // Lars Viklund ________________________________________ From: [email protected]<mailto:[email protected]> <[email protected]<mailto:[email protected]>> on behalf of Paul Melis <[email protected]<mailto:[email protected]>> Sent: Wednesday, July 11, 2018 13:39 To: [email protected]<mailto:[email protected]>; Caspar van Leeuwen Subject: Re: [easybuild] Loading toolchain module and CC/CXX env vars On 11-07-18 13:27, Caspar van Leeuwen wrote: > Curious to hear what you (and others) think. Also, apart from Juelich, > are other institutes running into the same problems that we are, and is > are the buildenv blocks/configs also the way they solve it? For > uniformity and reusability of EasyBlocks/Configs I think it would be > good if 'we, the community' adopt a uniform solution for this issue. Judging by the fact that there's only buildenv modules for three intel toolchains (and none for e.g. foss) I guess these aren't actually used that much and/or only in very specific circumstances? Paul -- Paul Melis | Visualization group leader & developer | SURFsara | | Science Park 140 | 1098 XG Amsterdam | | T 020 800 1312 | [email protected]<mailto:[email protected]> | www.surfsara.nl<http://www.surfsara.nl> | -- Dr. Bart E. Oldeman | [email protected]<mailto:[email protected]> | [email protected]<mailto:[email protected]> Scientific Computing Analyst / Analyste en calcul scientifique McGill HPC Centre / Centre de Calcul Haute Performance de McGill | http://www.hpc.mcgill.ca Calcul Québec | http://www.calculquebec.ca Compute/Calcul Canada | http://www.computecanada.ca Tel/Tél: 514-396-8926 | Fax/Télécopieur: 514-396-8934
