It depends on your use of the library. LGPL was planned mainly for libraries compiled to machine code. LGPL requires you to publish the full code of a library (library is usually in another file like .dll, .so), but not your software. It is required to publish your software under LGPL or GPL only if you copy parts of the library into your code base. The LGPL does require that it is allowed and possible for an end-user (assuming they have enough technical knowledge) to rebuild the application with a different, binary compatible, version of the LGPL library. If you don't use the dynamic linking facilities of your OS, you may have to distribute source and/or object files corresponding to your code to facilitate that requirement.
But LGPL allows you to share your software as SaaS, because you don't distribute it (AGPL "repairs" this "legal loophole"). So, if your software is SaaS, you are probably safe.
If your software is distributed to users, and you only use library APIs from code, but require users to have libraries already installed, you are probably safe too.
If you modify a library and still link it dynamically, you must publish the library source code under the LGPL or GPL.
If you use parts of library code in your software, you must distribute your software under the LGPL or GPL.
I know the question is old, and you probably found the solution, but maybe this answer will help other people.
This is not legal advice