Thank you all for your responses, however, I don't have 2013_sp1.2.144 yet, so 
I will just make a temporary version of this using 2013_sp1.1.106 until I can 
get 2013_sp1.2.144 (I am not in charge of getting this).
________________________________________
From: [email protected] [[email protected]] On 
Behalf Of Pablo Escobar Lopez [[email protected]]
Sent: Wednesday, March 19, 2014 4:12 AM
To: [email protected]
Subject: Re: [easybuild] Postprocessing Error

Hi Keith,

In case it's useful for you, I recently added this pull request

https://github.com/hpcugent/easybuild-easyconfigs/pull/747

Pablo.


2014-03-18 23:45 GMT+01:00 Fotis Georgatos 
<[email protected]<mailto:[email protected]>>:

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







--
Pablo Escobar López
HPC systems engineer
Biozentrum, University of Basel
Swiss Institute of Bioinformatics SIB
Email: [email protected]<mailto:[email protected]>
Phone: +41 61 267 15 82
http://www.biozentrum.unibas.ch

Reply via email to