https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118009
--- Comment #3 from Sam James <sjames at gcc dot gnu.org> --- (In reply to Andrew Pinski from comment #2) > This does not make sense: > > When GCC was built w/ fixincludes enabled, an old fixincluded'd version of > > the headers is used which has the old time64 macro, and therefore > > __pthread_cond_timedwait64 isn't being made available. > > If you install a new version of glibc, you need to rerun fixincludes (which > does get installed these days and had for a long time now). It makes sense, I just had no idea you could do that ;) Just to check, you're saying the following: * gcc installs a fixincludes (or whatever) binary/script if enabled called $tool * it can be run to regenerate include-fixed; * we should run it at least after installing critical packages if $tool is installed ? If so, that sounds reasonable and I'll wire that up on our end. All of the fixincludes hackery on our side was inherited from a loooooooong time ago and didn't mention any of that or handle it.