https://bugs.kde.org/show_bug.cgi?id=338252
--- Comment #19 from Дилян Палаузов <dilyan.palau...@aegee.org> --- A waring like "a plugin is needed to handle lto objects" suggests that nm/ar do not find the LTO plugin. For an object file compiled with LTO (and -fno-fat-lto-objects), `nm x.o` will print the symbols there, after it recognizes, that a plugin is needed. If the plugin is not findable by nm, it prints nm: libcoregrind_amd64_linux_a-m_poolalloc.o: plugin needed to handle lto object For the plugin support I have: ls /usr/local/lib/bfd-plugins/ -l total 4 lrwxrwxrwx 1 root staff 65 Mar 14 10:55 liblto_plugin.so -> /usr/local/libexec/gcc/x86_64-pc-linux-gnu/8.0.1/liblto_plugin.so This location is used by ar, ranlib and nm, but not by ld. I asked at https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84861 how to tweak coregrind/m_libcsetjmp.c so that -flto does not delete VG_MINIMAL_LONGJMP and VG_MINIMAL_SETJMP. I guess you have uploaded PRs with the ar crashes. -- You are receiving this mail because: You are watching all bug changes.
