Maxime Boissonneault

I am not sure why the tests are not actually running... Any idea @ocaisa ?

I tried to resolve the conflicts by cherry-picking all missing commits to this file and manually fixing the conflict when cherry-picking the commit that caused it, but Github still does...

> The failing test for Clang 11 is related to the sanity check, there is no `lib/libomptarget.rtl.x86_64.so`. That's not related to this PR though, so no need to fix here....

🤔 I do have these warnings as well, but somehow the sanity checks did not fail for my build, even though those libraries are indeed missing. I'll need to investigate...

``` == 2022-10-14 06:28:44,906 build_log.py:266 INFO sanity checking... == 2022-10-14 06:28:44,908 easyblock.py:3820 INFO Starting sanitycheck step == 2022-10-14 06:28:44,909 easyblock.py:3828 INFO Running method sanity_check_step part of step sanitycheck == 2022-10-14...

Ah, I guess we should set `enhance_sanity_check` in our hooks

I'm not sure if using `LLVM_ENABLE_RUNTIMES` works or not. See https://github.com/llvm/llvm-project/issues/59068

> Thanks for all the hard work @mboisson ! 🥳

It seems like adding `-DAF_BUILD_FORGE=ON` installed `libforge.so.1`. This should be enabled by default if the built libraries are linked on that. Additionally, I built using an external `spdlog`, which therefore...

For what it's worth, this is the patch I applied to our local build https://github.com/ComputeCanada/easybuild-easyconfigs/blob/computecanada-main/easybuild/easyconfigs/a/ArrayFire/ArrayFire-3.9.0-CMakeList.patch