On Tue, Feb 10, 2015 at 4:58 PM, Fotis Georgatos <[email protected]> wrote:
> Hi Malcolm, Kenneth, *, > > On Feb 10, 2015, at 11:44 PM, Kenneth Hoste <[email protected]> > wrote: > > For an updated version of goolf, which uses the last version of most of > the components (it's using GCC 4.8.4 rather than the latest-and-greatest > GCC 4.9.2), see the easyconfigs that were merged into the develop branch of > EasyBuild via pull request #1294, see > https://github.com/hpcugent/easybuild-easyconfigs/pull/1294/files. > > Compatibility arguments make 4.8.4 a better pick for the rest of HPC > ecosystem, today. > There are some reference URLs in the intro comment of that PR for the > interested reader. > > > And it gets better: you don't have to download or copy-paste each of the > easyconfig files in there yourself, you can let EasyBuild do it for you via > the --from-pr command line option. > > > > Try this: > > > > eb --from-pr 1294 -Dr > > Unfortunately, that one we tried today and didn’t work :) for a reason > fixed like this: > > eb --from-pr 1294 -Dr <something> # something is a directory which > has g/GCC/GCC-4.8.4 > > It relates to the fact that GCC/4.8.4 was in develop branch and #1294 > builds atop that. > > Alternatively, if you have a github account you may try to use in this way: > > https://easybuild.readthedocs.org/en/latest/Installation_Alternative.html?highlight=develop#installation-of-latest-development-version-using-provided-script > (this has worked for me in many tough-to-crack situations) Hi Fotis & Robert, Kenneth, Trusting Fotis on the toolchain compatibility arguments, I tried to take his suggestion with the hopes of next being able to ` eb --from-pr 1294 -Dr`, as suggested. But, following the linked-to recipe ... ..the install works fine as: curl -O https://raw.githubusercontent.com/hpcugent/easybuild-framework/master/easybuild/scripts/install-EasyBuild-develop.sh bash install-EasyBuild-develop.sh hpcugent /tmp/n/local/hpcbc/2015-02-12/Linux/x86_64/software/EasyBuild/head However, the following two issues arise: First) The `module load` statement need as provided in the recipe errors. Perhaps at one time `moeul load` accepted a full path to a module? It seems not to now. Look: trying it as suggested gives error: $ module load /tmp/n/local/hpcbc/2015-02-12/Linux/x86_64/software/EasyBuild/head/module-EasyBuild-develop Lmod has detected the following error: The following module(s) are unknown: "/tmp/n/local/hpcbc/2015-02-12/Linux/x86_64/software/EasyBuild/head/module-EasyBuild-develop" Please check the spelling or version number. Also try "module spider ..." However, breaking them into a `module use` followed by `module load` does work: bash-4.2$ module use /tmp/n/local/hpcbc/2015-02-12/Linux/x86_64/software/EasyBuild/head bash-4.2$ module load module-EasyBuild-develop bash-4.2$ eb --version This is EasyBuild 2.0.0dev (framework: 2.0.0dev, easyblocks: 2.0.0dev) on host mango.sgc.loc. ... moving on to the second issue: I now find that calling eb with no args fails: $ eb == temporary log file in case of crash /tmp/easybuild-Fd0O7k/easybuild-WJjBpW.log Traceback (most recent call last): File "/tmp/n/local/hpcbc/2015-02-12/Linux/x86_64/software/EasyBuild/head/easybuild-framework/easybuild/main.py", line 335, in <module> main() File "/tmp/n/local/hpcbc/2015-02-12/Linux/x86_64/software/EasyBuild/head/easybuild-framework/easybuild/main.py", line 237, in main log=_log, opt_parser=eb_go.parser, exit_on_error=not testing) File "/tmp/n/local/hpcbc/2015-02-12/Linux/x86_64/software/EasyBuild/head/easybuild-framework/easybuild/tools/build_log.py", line 197, in print_error opt_parser.print_shorthelp() File "/tmp/n/local/hpcbc/2015-02-12/Linux/x86_64/software/EasyBuild/head/easybuild-framework/vsc/utils/generaloption.py", line 507, in print_shorthelp self.print_help(fh) File "/tmp/n/local/hpcbc/2015-02-12/Linux/x86_64/software/EasyBuild/head/easybuild-framework/vsc/utils/generaloption.py", line 526, in print_help OptionParser.print_help(self, fh) File "/usr/lib64/python2.7/optparse.py", line 1669, in print_help file.write(self.format_help().encode(encoding, "replace")) File "/tmp/n/local/hpcbc/2015-02-12/Linux/x86_64/software/EasyBuild/head/easybuild-framework/vsc/utils/generaloption.py", line 478, in format_help result.append(self.format_description(formatter) + "\n") File "/tmp/n/local/hpcbc/2015-02-12/Linux/x86_64/software/EasyBuild/head/easybuild-framework/vsc/utils/generaloption.py", line 440, in format_description description = formatter.format_description(self.get_description()) File "/usr/lib64/python2.7/optparse.py", line 268, in format_description return self._format_text(description) + "\n" File "/usr/lib64/python2.7/optparse.py", line 264, in _format_text subsequent_indent=indent) File "/usr/lib64/python2.7/textwrap.py", line 366, in fill return w.fill(text) File "/usr/lib64/python2.7/textwrap.py", line 338, in fill return "\n".join(self.wrap(text)) File "/usr/lib64/python2.7/textwrap.py", line 329, in wrap return self._wrap_chunks(chunks) File "/usr/lib64/python2.7/textwrap.py", line 258, in _wrap_chunks raise ValueError("invalid width %r (must be > 0)" % self.width) ValueError: invalid width -2 (must be > 0) All this makes me leary about working with head at this point. Any advice here much appreciated on best way to get on board ` eb --from-pr 1294 -Dr ` ~Malcolm > > enjoy, > Fotis > > -- > echo "sysadmin know better bash than english" | sed s/min/mins/ \ > | sed 's/better bash/bash better/' # signal detected in a CERN forum > > > > > > > >
