https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104208
--- Comment #7 from Peter Bergner <bergner at gcc dot gnu.org> --- (In reply to Jakub Jelinek from comment #6) > I think the glibc problem is in a compiler defaulting to -mabi=ieeelongdouble > they want to use -mabi=ibmlongdouble -mlong-double-64 (because > -mabi=ibmlongdouble is added into CFLAGS everywhere early, and > -mlong-double-64 > is needed for a few TUs). > That wouldn't be diagnosed in the #c4 case, -mabi=ibmlongdouble is used while > -mlong-double-128 is in effect, so valid case. > -mlong-double-64 -mabi=ibmlongdouble > would be diagnosed though (-mabi=*double while -mlong-double-64 in effect). If that's the case, then I'll spend some time trying your suggestion. Florian, can you confirm that -mlong-double-64 comes after the -mabi=ibmlongdouble option in the problematical glibc build?
