https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82048
--- Comment #3 from joseph at codesourcery dot com <joseph at codesourcery dot com> --- On Fri, 1 Sep 2017, aaro.koskinen at iki dot fi wrote: > 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. That's <https://sourceware.org/bugzilla/show_bug.cgi?id=21987> (only applies if you are building for 64-bit with the headers installed from a 32-bit glibc build). Someone using 2.25/2.26 branches on SPARC may wish to backport my fix to those branches following the usual glibc release branch rules (use git cherry-pick -x, post to libc-stable when backporting, remember to update the NEWS file on the branch to include the entry for the fix that scripts/list-fixed-bugs.py would add at release time since we don't make point releases from branches or track branch state of bugs in Bugzilla).
