Hi,
Now that I have installed a couple of packages with easybuild I have a
surprising number of modules and realise that I should have been using
--hide-deps. I have two questions about this:
1. Is there any way to retrospectively hide modules, other than tweaking
the module files by hand,
Dear Christian,
On 22/11/2018 08:55, Christian Meesters wrote:
Dear all,
Sites supporting life-science users might have realized, that modules
installed with BLAST+* configfiles carry a glitch. I am writing in the
event that you have not yet realized that:
The installed modules will
So I tried compiling HDF5 this morning by hand using all EB CFLAGS as
well as the mentioned extra "-D_FloatXX" flags and it is definitely a
configure (autoconf) issue and how it handles the spaces in e.g.
"-D_Float64=*long double*" when parsing the CFLAGS variable.
At the moment I cannot find
Dear Bart
why not define it simply to double instead of "long double"?
this actually worked out! Thank you for the hint and explanation! It
doesn't really solve the problem of spaces in CFLAGS arguments parsed by
configure... but this is really good enough for my purpose.
@Åke, sorry your
Hey,
I just noticed that library versions are not necessarily used
consistently within one toolchain. For example, in foss-2018b,
there's both Bison-3.0.4 and Bison-3.0.5:
$ grep Bison */*/*.eb | grep foss-2018b
b/bioawk/bioawk-1.0-foss-2018b.eb:builddependencies =
[('Bison',
Dear Andres,
We've been keeping a close (automated) eye on which dependencies are
used in recent common toolchains (foss* & intel*, since 2018a) in that
respect: we have a test that verifies that there's only a single
"variant" (version + versionsuffix) of a software package used as a
Howdy Andreas and all,
For 2017b I tried to get ahead of the curve and submit
easyconfigs for the latest version of everything I could.
I maintain a list here of 2017b versions I should use.
I think it would be great if we could have a "definitive"
list of versions each time we start a new
Dear Kenneth,
thanks for the explanation!
Kenneth Hoste writes:
Dear Andres,
We've been keeping a close (automated) eye on which dependencies
are
used in recent common toolchains (foss* & intel*, since 2018a)
in that
respect: we have a test that verifies that there's only a single
Hi,
I know that Python 3.7 was dropped in the last release of EasyBuild due to
issues with some packages.
There are still packages that do not work with Python 3.7, although it has been
out for quite a while. Most notably tensorflow and Keras. I would therefore
suggest that you stick with
Dear Jakob,
On 22/11/2018 22:34, Jakob Schiøtz wrote:
Hi,
I know that Python 3.7 was dropped in the last release of EasyBuild due to
issues with some packages.
There are still packages that do not work with Python 3.7, although it has been
out for quite a while. Most notably tensorflow and
10 matches
Mail list logo
