take into account accelerator target when configuring EasyBuild

[boegel]

No description provided.

[eessi-bot]

Instance eessi-bot-mc-aws is configured to build for:

• architectures: x86_64/generic, x86_64/intel/haswell, x86_64/intel/skylake_avx512, x86_64/amd/zen2, x86_64/amd/zen3, aarch64/generic, aarch64/neoverse_n1, aarch64/neoverse_v1
• repositories: eessi-hpc.org-2023.06-compat, eessi-hpc.org-2023.06-software, eessi.io-2023.06-software, eessi.io-2023.06-compat

[eessi-build-deploy-bot-deucalion]

Instance boegel-bot-deucalion is configured to build for:

• architectures: aarch64/a64fx
• repositories: eessi.io-2023.06-software

[eessi-bot]

Instance eessi-bot-mc-azure is configured to build for:

• architectures: x86_64/amd/zen4
• repositories: eessi-hpc.org-2023.06-compat, eessi.io-2023.06-compat, eessi-hpc.org-2023.06-software, eessi.io-2023.06-software

[trz42]

We have to tweak the bot/check-build.sh so it recognises the modules/software under the different path. For example, see output in boegel#33 (comment) where module files and installed files are shown under 'other'.

[boegel]

@trz42 As discussed, this should be good to merge so we can start building CUDA software to be included in `software.eessi.io...

The improvements to bot/check-build.sh will be done in a follow-up PR

[boegel]

Testing of this was done in boegel#33, see last comment for success build of beagle-lib-4.0.1-GCC-12.3.0-CUDA-12.1.1.eb

[trz42]

lgtm, thanks a lot @boegel !