https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119089
--- Comment #8 from John David Anglin <danglin at gcc dot gnu.org> --- (In reply to Jonathan Wakely from comment #5) > Isn't this a glibc change, and you need to regenerate the gcc fixincludes > headers after updating glibc? That could have happened. Will investigate. Thanks for links.