LGPL and static linking?

Question

open source

Hello. The question is as follows:
Let's say there is a library that is currently difficult to compile dynamically, but you need to use it in a program with closed codes.
Wikipedia writes the following about this:
It is debatable whether the LGPL allows static linking
with proprietary software. The LGPL does not explicitly forbid static
linking (the term is not even used in the license) and there is
currently no precedent to prove otherwise. A number of commercial
programs use static linking with libraries
distributed under the LGPL
But at the same time, I heard from many programmers that it is necessary to open codes with static linking. What do you think: was it necessary and were there really precedents?

Answer 1

According to the LGPL, it is not necessary to open the code with static linking. OR source codes OR object files must be available so that the program can be relinked with another version of the library. At the same time, they are available only to those to whom you give your program.

Answer 2

There is also a prooflink to Habr with an exhaustive answer.