Hi Joachim,
On 11/02/16 12:14, Joachim Hein wrote:
Hi,
We just build a PGI compiler using PGI-15.10-GCC-4.9.3-2.25.eb and had
some fun with the license handling. We use flexlm and set an
env-variable (LM_LICENSE_FILE). The icc easyconfigs can handle this,
the PGI config does not. In the end we created a dummy licences file
(EasyBuild seems only to check for the existence) and modified the
module file for what we need. So we can now continue.
Using an
export [email protected] <mailto:[email protected]>
type statement did not make things build. It does for the icc. When
comparing the easy-configs (PGI and ICC) I didn’t notice the obvious
difference, so that should be in the easyblock. I am wondering
whether some with better expertise on those could have a look and
“upgrade” the PGI.
There's indeed a bit of magic going on for the Intel tools, that could
be useful in other places as well (in the easyblock for PGI, but also in
other places).
The IntelBase generic easyblock, which serves as a base for the
different easyblocks for the Intel compilers/libraries/tools, has the
magic in configure_step [1].
We could look into fleshing this out into a function to framework, such
that the IntelBase and PGI (and other) easyblocks can easily call out to it.
Things are a bit entangled in IntelBase.configure_step right now (some
things in there are really specific to the Intel tools), so this is not
exactly trivial, but definitely doable.
And now the million dollar question: who's up for it? :-)
regards,
Kenneth
[1]
https://github.com/hpcugent/easybuild-easyblocks/blob/7fe31aa39dd2196298e1f2e328271c9f1d766baa/easybuild/easyblocks/generic/intelbase.py#L204
