Arch Linux User Repository

Any chance you can make a patch and send it to me via mail?

@Svenstaro: Thanks for the new package. I've only just noticed that your new package in Community doesn't provide the mkl_link_tool command (more information here). Would you mind including mkl_link_tool in your package?

@huyizheng This package includes the static libraries (with extensions *.a), while the [community] package only includes the dynamic ones.

I packed this package and it's intel-mkl package has 1622.47 MiB installed size, while the one in community repo only has 714.7 MB installed size. Why the size difference between these two package is so big?

mklvars.sh is a terrible script that I'll ship for compatibility reasons. However, I'll likely just put some static paths in there. pkg-config should be preferred. I'll add pkg-config support sometime later (though patches welcome if you like to help!).

@Svenstaro , one main difference is that the split package provides a bin directory with additional scripts for setting up the environment, such as /opt/intel/mkl/bin/mklvars.sh .

Can you port this over please?

Ok check the new package. It should be basically completely compatible with the way things were packages in this current split package. You can probably just remove your split package without any consequences.

I'll likely change intel-mkl to install to /opt/intel/mkl instead as that seems to be what intel expects. New package coming in a bit.

@Svenstaro That's great! I haven't tried it yet, but it would make building packages like r-mkl so much easier.

A couple of questions.

The split intel-mkl provides: /etc/intel-mkl-th.conf /etc/ld.so.conf.d/intel-mkl.conf /etc/profile.d/intel-mkl.sh Do you think whether these could be supported in some way by the [community] package?

I'm happy to switch this package to rely on [community] intel-mkl. But then, I guess, there should be some version compatibility/synchronization mechanisms implemented (I guess Parallel Studio releases are a bit delayed in comparison to just MKL, so there could be problems during these "transition" periods). Do you have any recommendations for how it's better be done?

Or is it easier just to rename the AUR intel-mkl package to something else (what would be your suggestion of the name)?

Thank you Sven, I suggest that your [community] package for intel-mkl should have optional dependencies on intel-tbb and openmpi for TBB and BLACS support respectively. Otherwise, it works well with some simple ScaLAPACK programs I've tested it with.