Summary: | gcc-12 (HEAD) can't compile glibc due to new arch-specific ISO_Fortran_binding.h header in gcc-12 | ||
---|---|---|---|
Product: | glibc | Reporter: | Sergei Trofimovich <slyich> |
Component: | build | Assignee: | Not yet assigned to anyone <unassigned> |
Status: | RESOLVED OBSOLETE | ||
Severity: | normal | CC: | carlos, dilfridge, sam, sandra.oss, toolchain |
Priority: | P2 | ||
Version: | 2.34 | ||
Target Milestone: | --- | ||
See Also: |
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101305 https://bugs.gentoo.org/show_bug.cgi?id=833620 |
||
Host: | Target: | ||
Build: | Last reconfirmed: |
Description
Sergei Trofimovich
2021-08-03 20:04:33 UTC
Proposed simple extension of `include` discovery as https://sourceware.org/pipermail/libc-alpha/2021-August/129808.html Apparently the underlying change was backported to the gcc-11 branch (where we now see it in Gentoo in a recent snapshot). (In reply to Andreas K. Huettel from comment #2) > Apparently the underlying change was backported to the gcc-11 branch > (where we now see it in Gentoo in a recent snapshot). We seem to be hitting something else (which looks very similar), sorry. I believe gcc rolled arch-specific headers back in https://gcc.gnu.org/git/?p=gcc.git;a=commitdiff;h=13beaf9e8d2d8264c0ad8f6504793fdcf26f3f73 Thus not an immediate failure. Given that there was no feedback at all on the ML or IRC and I don't use multilib gccs I'm closing it as OBSOLETE. |