Hi Bart, On 26 Sep 2013, at 23:40, Bart Verleye wrote:
> Hi, > > I'm still struggling a bit with the installation of the new toolchain. > There are chains/software called *mpich* but there is also e.g. mvapich2. It > seems I couldn't decide if I would use the 2 or not, and now I get this error: > > ERROR: EasyBuild encountered an exception (at easybuild/main.py:833 in > build_and_install_software): autoBuild Failed (last 300 chars): EasyBuild > crashed with an error (at easybuild/tools/toolchain/toolchain.py:328 in > prepare): List of toolchain dependency modules and toolchain definition do > not match (set(['MPICH', 'GCC', 'FFTW', 'ScaLAPACK', 'OpenBLAS']) vs > set(['GCC', 'MPICH2', 'FFTW', 'ScaLAPACK', 'OpenBLAS'])) > > I got the MPICH vs. MPICH2 error before, thought I resolved it, but clearly I > haven't. Would you have an idea what I did wrong? I attached some files that > might be of interest. The EasyBuild framework contains a hard check to see if the toolchain definition in the framework (your gmpolf.py) matches the list of dependencies in the easyconfig file (gmpolf-X.eb, which you didn't provide). In gmpolf.py, you specify that toolchain includes MPICH2 (not MPICH), and thus it's also enforced as such by the framework. If you want gmpolf.py to include MPICH (and not MPICH2), you should define the gmpolf toolchain as such in gmpolf.py. Can you also provide us your gmpolf-X.eb easyconfig file? If you need help, I'm available on Skype right now (kehoste), for the rest of (the/my) day (mostly). > A second question I have concerns github. Eb does not support github sources, > right? Is the solution then to download the source as a zip file and make a > link to the local zip? We don't have support for GitHub sources yet, no, but we'd like to add it (soon) [1]. For now, your best option is to create a tarball (or zip file, if you want) and give it a proper version number (and maybe a datestamp). We realize that's tedious and make it hard to make the build reproducable for others, but it'll have to do for now. > Thank your for all the work on the custom module naming, and good luck with > the new version! If the custom module naming support something you would be using? If so, don't hesitate to try it out soon and provide us with some feedback, we'd love to hear how we can improve it (because we will, see [2]). [1] https://github.com/hpcugent/easybuild-framework/issues/112 [2] https://github.com/hpcugent/easybuild-framework/issues/687 regards, Kenneth
