Maxime Boissonneault

That is not possible either. There are multiple versions of the CUDA toolkit installed, and there is not a single one of them that is prioritized. Users load the ArrayFire...

Note that our *linker* already knows where to look (hence why the correct RPATH are set in the library's shared objects). Linkers use `LIBRARY_PATH`, *NOT* `LD_LIBRARY_PATH` which is meant for...

Speaking as a package manager/software install for large HPC clusters, we very much prefer having releases (with sane versioning schemes) than having commit hashes and having to make up our...

> Please run `preconfigure.py --help` and see if it addresses what you need You mean the script in the `legacy` folder ? It does not provide any flag to tell...

> Hi, so in your case, su2 _didn't_ compile on your system using the auto-downloaded tools, but by using the existing system-wide installation of the tools, it _did_ compile? Or...

There's no using the develop branch. Develop software don't make their way in our module systems, we only install releases, with tarbals of the sources and checksums of those tarballs,...

> Yes but it would be kind of you to check if a feature of a future release is going in the direction of what you need. Compiled libraries would...

Hitting the same issue. Need to downgrade setuptools to

This seems to have disappeared for me with recent versions of setuptools and/or numpy

To be more specific, after more testing, `setuptools>63` is broken to build `numpy=1.24` builds fine with the latest `setuptools`.