LGPL absolutely does care about linking. Section 4d specifically talks about shared libraries and requires you to be able to "re-link" the application with a modified version of the library, if dynamic linking is not used.
When people talk about how the LGPL isn't a good license, it's largely because A) C and C++ are really the only two systems languages for which dynamic linking is even an option and B) header-only libraries, templates/generics, and heavy use of inlining can make "re-linking" a statically linked executable basically impossible.
Yeah the LGPL gets a little technical, but at ita core it's really just saying there needs to be a way for the user to replace the LGPL library that is used.
If it was statically linked on then some sort of relink ability needs to be provided.
It's more like advice for people who want to incorporate LGPL software.
When people talk about how the LGPL isn't a good license, it's largely because A) C and C++ are really the only two systems languages for which dynamic linking is even an option and B) header-only libraries, templates/generics, and heavy use of inlining can make "re-linking" a statically linked executable basically impossible.