https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82048
--- Comment #2 from Aaro Koskinen <aaro.koskinen at iki dot fi> --- (In reply to Eric Botcazou from comment #1) > This looks like an issue with your libc. Where does __nldbl_fprintf come > from? It seems this was introduced by GLIBC 2.25. GCC does not define __LONG_DOUBLE_128__ with -m64 on SPARC so functions are redirected to __nldbl_* versions.
