How to handle gaps in the and discrepenties between Aarch64 and X86_64

For some packages like LAMMPS and bcgTree. The dependencies are different on the Aarch64 and X86_6.

This means that are some build that do not have modules for all the targets.

• https://www.eessi.io/docs/available_software/detail/ScaFaCoS
• https://www.eessi.io/docs/available_software/detail/RAxML/
• https://www.eessi.io/docs/available_software/detail/tbb/

We should come to a conclusion on this. Because we seem to be returning to the same discussion.

Should we build empty module for ScaFaCoS and RAxML-avx12 on ARM targets. To make it clear why they are not their.

Should we deploy RAxML-standard on all targets even though it only makes sense to have on the targets that are not compatible with avx12.

I also see some tbb installations are build on all targets. So we should also see if it still needs to be disabled for LAMMPS on ARM targets.