Hi Chandler,

On Apr 15, 2015, at 4:41 PM, Chandler Wilkerson <[email protected]> wrote:
> It would be greatly helpful if we could identify the specific arch, and 
> filter out, say ppc64 rpm based builds on an ubuntu ppc64el system. (and I'd 
> also like to take a pass on the Intel compilers and their many child packages 
> and toolchains)

AFAIK, nobody has a solution of the type, although all understand the eventual 
need for it.
ie. the show, currently, is largely run around x86_64 builds because that’s 
where all the testing is done.

If anybody implements something around this concept, please be kind and 
consider configure strings:
https://gcc.gnu.org/gcc-4.1/buildstat.html # fi. powerpc64-unknown-linux-gnu
https://gmplib.org/devel/tm-date.html

> Would this be a feature request, or is it implementable with some better 
> knowledge of the EasyConfig setup?

IMHO, it is quite clearly a feature request and here is the why:

- if varying builds are merged within easyconfigs, too many conditionals emerge:
  
https://github.com/hpcugent/easybuild-easyconfigs/blob/master/easybuild/easyconfigs/c/CUDA/CUDA-5.0.35-1.eb
- dependencies on specific arch variations, really imply different builds (look 
sanity steps and later):
  
https://github.com/hpcugent/easybuild-easyconfigs/blob/master/easybuild/easyconfigs/p/PDT/PDT-3.19-ictce-5.3.0.eb
- mangling too much `versionsuffix` is not an optimal idea because it distorts 
your namespace
  Having your namespace arch-free allows you fi., to swap 64bit builds with 
32bit and vice versa

best,
Fotis


-- 
echo "sysadmin know better bash than english" | sed s/min/mins/ \
  | sed 's/better bash/bash better/' # signal detected in a CERN forum






Reply via email to