Hi Ke*,
On Mar 18, 2014, at 10:45 PM, Kenneth Hoste wrote:
> But it should still look in the configured source path too though. Are you
> saying that's not the case when --try-amend is used?
to save all the brain-cycles, he mentioned to store the tarballs next to .eb
files,
so that explains it all: as soon as --try is employed, that relationship is
broken,
because the intermediary easyconfigs end up in temporary locations.
Also, I just recall that the true check for the license server w. icc/ifort is
better
done with "icc -V", to force a check-in/check-out on the flexlm server.
Otherwise,
do not rely too much in Intel's installation mechanisms for symmetric
attitude...
(ie impi checks at install time, icc/ifort do not; and worse: failure modes may
be hidden)
btw. If you found some sanity check that is worthy to consider at install time,
open an issue to check its merit.
Finally, yes Keith, that's what we all do when we need to explore a new
toolchain:
* pick a toolchain combo that works reasonably well for your site (fi. iomkl
variant)
* parse other easyconfigs (eg. via sed) and produce the desired configurations
* iterate over the new set providing the builds (fingers crossed), with 'eb'
command
(you can also do the robot thingy, if you have preserved the directory
structure and renamed files)
We all agree that something like the above could eventually become a oneliner,
but we don't have that yet :-P
When the build operations do not deviate across toolchains, things will just
magically work.
When they do deviate though, welcome to the world of EasyBuild, here is your
turn to contribute back :)
best,
Fotis
--
echo "sysadmin know better bash than english" | sed s/min/mins/ \
| sed 's/better bash/bash better/' # Yelling in a CERN forum
