Re: [easybuild] How to build modules compiled for different hardware architectures?

The present thread contains many excellent suggestions. In order to keep life simple, I've chosen to maintain separate EB trees for each CPU-architecture. One question remains: How to determine the current host's CPU-architecture. The best solution I've been able to find is to use GCC 4.9

Re: [easybuild] How to build modules compiled for different hardware architectures?

Hi, On Tue, Oct 4, 2016 at 12:06 PM Pablo Escobar Lopez < pablo.escobarlo...@unibas.ch> wrote: > * We have 3 geographically distributed sites and would like to be able to > compile once and then rsync to the others. We are still running into > problems if we aren't carefully selecting the host

Re: [easybuild] How to build modules compiled for different hardware architectures?

2016-10-04 11:49 GMT+02:00 Martin : > > > * Within R users are loading the module and doing install.packages() > on a random node, later they want to use that package on a script and it > gives "random" errors with illegal instruction depending on where it ran. > -- User

Re: [easybuild] How to build modules compiled for different hardware architectures?

Hi I don't have any kind of record that would be useful. >From memory a few cases where this happened: * Within R users are loading the module and doing install.packages() on a random node, later they want to use that package on a script and it gives "random" errors with illegal instruction

Re: [easybuild] How to build modules compiled for different hardware architectures?

Hello Martin, On 1 Oct 2016 12:57 am, "Martin" > wrote: > > I think this is a recurring question. > My impression is that "HPC" seems to somehow imply that there's a divide in people. > > With quite some exxageration: > One group wants to

Re: [easybuild] How to build modules compiled for different hardware architectures?

I think this is a recurring question. My impression is that "HPC" seems to somehow imply that there's a divide in people. With quite some exxageration: One group wants to squeeze out every possible CPU cycle and in turn is willing to invest the time to recompile multiple times, even within the

Re: [easybuild] How to build modules compiled for different hardware architectures?

I like Pablo's trick of checking arch before building. Good idea in my book. I do something similar here (as EasyBuild-ada-Westmere) [attached]. jack On 09/29/2016 03:00 AM, Pablo Escobar Lopez wrote: I use a similar solution. I have /soft/apps/arch1 /soft/apps/arch2/soft/apps/archN in

Re: [easybuild] How to build modules compiled for different hardware architectures?

What we are aiming for is a combination. The achitecture independent code (like EasyBuild itself, intel and portland compilers and similar) are installed under /eb/common/ The arch dependent packages are under /eb/opt/... which is mounted per client architecture/OS distro version, from the

[easybuild] How to build modules compiled for different hardware architectures?

We're installing EasyBuild 2.9.0 on our new cluster, and user application codes should be built on top of the latest foss-2016 toolchain. Since our cluster has 4 different generations of Intel Xeon hardware (Nehalem, Sandy/Ivy Bridge, Haswell, Broadwell), users want to compile their