This is now the second request about this. I'm generally willing to add these if you can provide me with a proper practical real world example of why this is a good idea. The previous bug couldn't come up with a good example.

As the MKL libraries are big (or one could say "HUGE"), any custom software developed using MKL is often wise to link statically. E.g. having a Docker container installing all the shared Intel libs or just having a static executable is 700Mb vs 60Mb.

That said, this is not the most common scenario and might not justify increasing the size of this community package. That is exactly the reason I was arguing to keep the intel-mkl_psxe AUR package, as the people that install the whole intel toolchain are more likely to also need the static libs.

I much prefer not duplicating stuff so if you say this is likely to be a common use case and you're the second one to state so then I'm willing to just ship those libs in the package.

See if you like the new package.

Unfortunately, the most static libraries are still not included. For example, I'm missing opt/intel/mkl/lib/intel64/{libmkl_intel_ilp64.a,libmkl_sequential.a,libmkl_core.a}

Exactly the libs you describe are in the current package.

Ah sorry, the repo I use hadn't synced yet. Yes, this package contains all the static libraries needed and is great for use cases like mine. Thanks!