Hi, thanks for the information. At the moment I would like to avoid building different stacks. It seems my colleagues are opposed to that options as they feel it introduces uneeded complexity.
Personally I plan to revisit that option later when there is more confidence that this does actually work. Please if you can post the slides somewhere, references like these always help then I can say: "Look guys, these people have been doing it for years and it works. Why not just try it?" :) /Martin On Tue, Jul 14, 2015 at 6:05 PM Pablo Escobar Lopez < pablo.escobarlo...@unibas.ch> wrote: > Hi Martin, > > openblas will ignore the optarch option in easybuild but you can use > something like this in the OpenBLAS easyconfig > > buildopts = 'TARGET=SANDYBRIDGE BINARY=64 ' + threading + ' CC="$CC" > FC="$F77"' > > here you have the list of supported targets in openblas > https://github.com/xianyi/OpenBLAS/blob/develop/TargetList.txt > > If you want to share the same openblas installation across all your > different cpu types you will need to use the target which match your oldest > cpu. Another approach is to maintain a different software stack by cpu type > as described in the slides I attach (page 9) > > regards, > Pablo. > > > 2015-07-14 13:21 GMT+02:00 Martin <mar...@marcher.name>: > >> Hi, >> >> I have a couple of different CPUs and in my situation EB is not so much >> about a HPC site or repeatable build but rather about managing the stuff. >> So here's the thing: >> >> When using R/3.2.0-foss-2015a-bare (just a simply >> --try-software-version easyconfig) and subsequently installing a few R >> packages will work on one host but fail on another. >> >> The error is a classical illegal instruction in the underlying OpenBLAS >> library (I could reproduce this specific problem >> >> The problem is that OpenBLAS/0.2.13-GCC-4.9.2-LAPACK-3.5.0 seems to >> using some magic so that is is processor dependent. The processors involved >> are: >> >> * AMD Opteron(TM) Processor 6238 and >> * Six-Core AMD Opteron(tm) Processor 8431 >> >> There are also a few Intel processors and a few other AMD CPUs here. >> What I'm looking for is a setting for easybuild that optimizes for >> portability between compatible CPU architectures. >> >> Does anyone have suggestions how to achieve the most compatibility and >> care less about byte-level reproducability or performance? The target >> platform I have in mind is "64bit x86 compatible". >> >> I have optarch="" in my config.cfg where I thought that would already >> take care of it. >> >> Any thoughts would be appreciated. >> >> /Martin >> > -- >> -- >> http://www.xing.com/profile/Martin_Marcher >> http://www.linkedin.com/in/martinmarcher >> Mobil: +43 / 660 / 62 45 103 >> UID: ATU68801424 >> > > > > -- > Pablo Escobar López > HPC systems engineer > Biozentrum, University of Basel > Swiss Institute of Bioinformatics SIB > Email: pablo.escobarlo...@unibas.ch > Phone: +41 61 267 21 80 > http://www.biozentrum.unibas.ch > -- -- http://www.xing.com/profile/Martin_Marcher http://www.linkedin.com/in/martinmarcher Mobil: +43 / 660 / 62 45 103 UID: ATU68801424
