https://bugs.kde.org/show_bug.cgi?id=469049
--- Comment #3 from Paul Floyd <pjfl...@wanadoo.fr> --- (In reply to Dirk Mueller from comment #0) > /tmp/ccAV30QW.ltrans8.ltrans.o:/home/abuild/rpmbuild/BUILD/valgrind-3.20.0/ > memcheck/../coregrind/m_machine.c:2393: undefined reference to > `vgPlain_unknown_SP_update' > [ 97s] > /usr/lib64/gcc/powerpc64-suse-linux/13/../../../../powerpc64-suse-linux/bin/ > ld: /tmp/ccAV30QW.ltrans8.ltrans.o: in function `vg_SP_update_pass': > [ 97s] > /home/abuild/rpmbuild/BUILD/valgrind-3.20.0/memcheck/../coregrind/m_machine. > c:2393: undefined reference to `vgPlain_unknown_SP_update_w_ECU' > [ 97s] > /usr/lib64/gcc/powerpc64-suse-linux/13/../../../../powerpc64-suse-linux/bin/ > ld: > /tmp/ccAV30QW.ltrans8.ltrans.o:/home/abuild/rpmbuild/BUILD/valgrind-3.20.0/ > memcheck/../coregrind/m_machine.c:2393: undefined reference to > `vgPlain_unknown_SP_update_w_ECU' > [ 97s] > /usr/lib64/gcc/powerpc64-suse-linux/13/../../../../powerpc64-suse-linux/bin/ > ld: /tmp/ccAV30QW.ltrans8.ltrans.o: in function `vg_SP_update_pass': > [ 97s] > /home/abuild/rpmbuild/BUILD/valgrind-3.20.0/memcheck/../coregrind/m_machine. > c:2393: undefined reference to `vgPlain_unknown_SP_update' vgPlain_unknown_SP_update (aka VG_(unknown_SP_update)) is just an ordinary function in coregrind/m_stacks.c I can't see any conditional compilation that would cause it to be not compiled. There is this bit in coregrind/Makefile.am # The below files cannot be compiled with lto, otherwise that gives # undefined symbols at link time. So, define a noinst library to # build the needed .o with specific flags. # These objects are added to the libcoregrind library. NOLTO_COREGRIND_SOURCES_COMMON = \ m_libcsetjmp.c \ m_main.c Perhaps m_stacks.c needs to be moved there? Can you check with nm that vgPlain_unknown_SP_update is in libcoregrind-ppc64be-linux.a ? > STEPS TO REPRODUCE > 1. on openSUSE Tumbleweed configure with ./configure > --host=powerpc64-suse-linux-gnu --build=powerpc64-suse-linux-gnu > --program-prefix= --disable-dependency-tracking --prefix=/usr > --exec-prefix=/usr --bindir=/usr/bin --sbindir=/usr/sbin --sysconfdir=/etc > --datadir=/usr/share --includedir=/usr/include --libdir=/usr/lib64 > --libexecdir=/usr/libexec --localstatedir=/var --sharedstatedir=/var/lib > --mandir=/usr/share/man --infodir=/usr/share/info --enable-lto=yes Would it be possible to try a build with just "configure"? Or even just without --enable-lto=yes? -- You are receiving this mail because: You are watching all bug changes.