Dear EasyBuilders,
The next EasyBuild conf call is planned for today, Wed August 22nd 2018,
at 5pm CEST, see also
https://plus.google.com/events/cn6s7opf3a4cjf5jchjrf0cjni4 . My
apologies for the late reminder...
Current agenda:
* outlook to upcoming EasyBuild 3.7.0
* ETA: by end of Aug'1
Dear EasyBuilders and lmod users,
I have a question for the community. Currently EasyBuild supports to deploy
its software stack in a hierarchical manner, as intended and supported by lmod
(ie: load compiler, that expands $MODULEPATH and the MPIs become visible, load
an MPI, which expands $MOD
Dear Damian,
I think that this is a very good approach.
In principle, it should work for MPI implementations that are part of the MPICH
ABI initiative (https://www.mpich.org/abi/)
We do make use of this ABI compatibility for the container usage at Piz Daint
(https://user.cscs.ch/tools/container
>
> After using easybuild for several years our single largest issue is
> incompatible libraries used by packages in the same toolchain. We have
> educated our users to always use modules and to use modules that are in the
> same toolchain. Workflows can be very complex and users typically load ma
Dear EasyBuilders,
Notes for today's conf call are available at
https://github.com/easybuilders/easybuild/wiki/Conference-call-notes-20180822
.
Next conf call is planned for Wed Sept 5th, see also
https://plus.google.com/events/cpahr0kk2da3dbolpleldljndgg
regards,
Kenneth
On 22/08
I should have mentioned that we are jumping from 2016b to 2018b. 2016b
toolchain is full of inconsistent libraries.
Pull requests are automatically checked for duplicates (since a year or so back
I think?).
The first check-in for a given library wins. This does not sound like it is
curated, but
6 matches
Mail list logo