Hi Don,
On 13/03/15 16:44, Don Moore wrote:
Hi
Does anyone have a sketch on how to work through easybuild
modifying the *.eb files or even adding toolchains ?
If you're modifying easyconfig files, you should set up your own
easyconfigs repository/directory, and give that preference over the ones
that come installed with EasyBuild, see
http://easybuild.readthedocs.org/en/latest/Using_the_EasyBuild_command_line.html#controlling-robot-search-path
(which was updated/enhanced just yesterday).
For adding toolchains, see
https://github.com/hpcugent/easybuild/wiki/Compiler-toolchains.
Are you looking into defining a new toolchain that doesn't exist yet
(i.e. a new combination of toolchain components), or just a new version
of an existing toolchain?
The former requires plugging in the definition for the new toolchain
into the EasyBuild framework. In both cases, you'll need to compose an
easyconfig file to specify the
versions of the toolchain components.
I setup a github repo to keep track of changes that - I make.
When setting up robot-paths=/opt/apps/alteb , eb can find the
easyconfig files - but the builds fails because apparently the
infrastructure is not shared . My alteb only has the a..z
structure from easybuild/easyblocks . For now- I have to
overlay the easybuild/easyblocks from a tarball.
Hmm, you'll have to clarify this, I'm not sure I understand what your
problem is.
I'm not sure what you mean by "the infrastructure is not shared"?
Are you using a custom set of easyconfigs *and* easyblocks, next to a
full EasyBuild installation (framework+easyblocks+easyconfigs)?
Giving your own set of easyblocks preference over the ones installed
with EasyBuild is tricky, because of some magic we do to 'flatten'
easyblocks namespace (to kick out the 'letter' directory level, so you
can do "from easybuild.easyblocks.gcc import EB_GCC", etc.).
See
https://github.com/hpcugent/easybuild/wiki/Setting-up-your-own-easyblocks-repository
for more information on this.
regards,
Kenneth
