https://bugs.kde.org/show_bug.cgi?id=401742
--- Comment #12 from Bernhard M. Wiedemann <kdebugs...@lsmod.de> --- According to our compiler guys, such .a files should then be created with -ffat-lto-objects so that they contain actual machine code that can be used without having the same gcc version and lto-plugins. In openSUSE, header files and .a files are mixed together in a valgrind-devel package and that is used in builds of anjuta ceph gperftools libqt5-qtwebengine mpich rdma-core ruby2.5 wine xmms2 But maybe they only use the .h files. I quickly tested xmms2, rdma-core, gperftools, anjuta and none of the 4 uses .a files. Anyway, such a patch seems useful: valgrind-3.14.0/configure.ac: -TEST_LTO_CFLAGS="-flto -flto-partition=one -fuse-linker-plugin" +TEST_LTO_CFLAGS="-flto -flto-partition=one -fuse-linker-plugin -ffat-lto-objects" That would allow us to strip the LTO sections from the .a files and still have the normal machine code. Or we just drop the .a files from our rpms since nobody seems to use them. -- You are receiving this mail because: You are watching all bug changes.
