If I understand correctly, the LGPL v2.1 (and the subsequent licenses) allow an user to link a proprietary program to the LGPL licensed library as long as the open source library can be modified and re-linked.
However, what happens if one wishes to link an LGPL software to a proprietary library? I am also confused about why LGPL treats everything as a library.
For example, there is a scientific software routinely used in my field, which is released under the LGPL v2.1. When compiled, the source code produces an executable (and also a library that other softwares can link to). Now, the software needs a BLAS and LAPACK routines, which can be provided by Intel MKL a.k.a. Math Kernel Library. However, Intel MKL is proprietary code. Their simplified software license does allow redistribution of everything (headers, static libraries, dynamic libraries).
Now the thing is that the scientific software does not provide precompiled binaries and only provides source code, which I think causes a lot of problems to beginners in the field. So, I want to distribute precompiled binaries of the software linked to Intel MKL (for free of course). The linking can be static or dynamic.
Am I allowed to do this? I am new to open source, so an explanation in simple words would be the most helpful.
There is another post here that is similar, but I do not understand how linking to the library and from the library are different. I have tried reading the LGPL v2.1 license, but there does not seem to be anything distinguishing them.