https://bugs.kde.org/show_bug.cgi?id=457712
--- Comment #5 from Christophe Leroy ---
Discussion on the list at
https://sourceforge.net/p/valgrind/mailman/valgrind-developers/thread/6ec51692-b1cb-0382-e132-5ad765f07dad%40csgroup.eu/#msg37668256
--
You are receiving this mail because:
You are
https://bugs.kde.org/show_bug.cgi?id=457712
--- Comment #4 from Christophe Leroy ---
I was previously using glibc 2.23 with gcc 5 and it was working perfectly as
the symbols where present in libgcc.
With gcc 11 and glibc 2.35 it doesn't work anymore because the symbols are not
anymore in l
https://bugs.kde.org/show_bug.cgi?id=457712
Christophe Leroy changed:
What|Removed |Added
Summary|Failed building valgrind|Failed building valgrind
https://bugs.kde.org/show_bug.cgi?id=457712
--- Comment #2 from Christophe Leroy ---
John Reiser suggested a work-around (see below). That doesn't work, I ended up
pulling the entire glibc objects and got conflicts with other symbols, I gave
up.
2. Possible work-around: Extract the mi
https://bugs.kde.org/show_bug.cgi?id=457712
--- Comment #1 from Christophe Leroy ---
Looking at gcc history, I found:
commit e610393ca76b204d861177a9ec542e2b4b3956cb
Author: Joseph Myers
Date: Thu Oct 30 17:28:30 2014 +
Make soft-fp symbols into compat symbols for powerpc*-*-linux
https://bugs.kde.org/show_bug.cgi?id=457712
Bug ID: 457712
Summary: Failed building valgrind (memcheck) for Linux
powerpc32 (undefined reference to `__floatsidf') with
recent glibc
Product: valgrind
Version: 3.19.