bug#27866: Handle clang's internal libraries when finding compiler's internal libraries
Martin Storsjö <[email protected]>
| Newsgroups | gmane.comp.gnu.libtool.bugs |
|---|---|
| Message-ID | <[email protected]> |
On Wed, 14 Aug 2019, Martin Storsjö wrote: > by manually setting this: > > lt_cv_deplibs_check_method=pass_all > > In other projects that don't set this, linking with libtool prints this > warning: > > *** Warning: Trying to link with static lib archive > C:/code/llvm-mingw/lib/clang/9.0.0/lib/windows/libclang_rt.builtins-x86_64.a. > *** I have the capability to make that library automatically link in when > *** you link to this library. But I can only do this if you have a > *** shared version of the library, which you do not appear to have > *** because the file extensions .a of this argument makes me believe > *** that it is just a static archive that I should not use here. > > Manoj, did you run into this issue anywhere? I see that libtool always sets lt_cv_deplibs_check_method=pass_all on Linux, so that's probably why you haven't run into it. So, it basically boils down to, what the actual purpose of inspecting dependency libs is (what real scenario does it protect from), as it breaks linking to compiler_rt's builtins (which are referred to as an absolute path to the .a file)? // Martin _______________________________________________ Bug-libtool mailing list [email protected] https://lists.gnu.org/mailman/listinfo/bug-libtool