https://bugs.kde.org/show_bug.cgi?id=457712
--- Comment #1 from Christophe Leroy <christophe.le...@csgroup.eu> ---
Looking at gcc history, I found:
commit e610393ca76b204d861177a9ec542e2b4b3956cb
Author: Joseph Myers <jos...@codesourcery.com>
Date: Thu Oct 30 17:28:30 2014 +0000
Make soft-fp symbols into compat symbols for powerpc*-*-linux*.
Continuing preparations for implementing
TARGET_ATOMIC_ASSIGN_EXPAND_FENV for powerpc*-*-linux* soft-float and
e500, this patch makes soft-fp symbols used for those targets into
compat symbols when building with glibc >= 2.19, so that they are only
in shared libgcc for existing binaries requiring them, not in static
libgcc and not available for new links using shared libgcc. Instead,
new links will get the symbols from libc, which has exported all of
them since 2.19. ....
I understand that:
- libc is required to get those symbols.
- valgrind is intentionaly linked without libc but with libgcc only (from
comments in coregrind/m_main.c)
--
You are receiving this mail because:
You are watching all bug changes.
