Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#74188 - [gcc] gcc-debug contains bogus /build dir
Attached to Project:
Arch Linux
Opened by Toolybird (Toolybird) - Tuesday, 22 March 2022, 06:28 GMT
Last edited by David Thurstenson (thurstylark) - Friday, 25 March 2022, 23:55 GMT
Opened by Toolybird (Toolybird) - Tuesday, 22 March 2022, 06:28 GMT
Last edited by David Thurstenson (thurstylark) - Friday, 25 March 2022, 23:55 GMT
|
Detailsgcc-debug seems to contain a stray /build dir (in addition to the expected stuff under /usr).
I haven't fully got my head around debug pkgs yet but surely this cannot be correct? It means the gcc-debug pkg is not installable in the build chroot immediately after a completed build due to file conflicts (many errors of type "blah exists in filesystem"). |
This task depends upon
Looking deeper, this is likely a pacman issue, and it might already be fixed by:
https://gitlab.archlinux.org/pacman/pacman/-/commit/ae2f506d
In fact, gcc-d is about to become harder to build in gcc-12. Similar to the gcc-ada situation, in gcc-12 gcc-d is required to bootstrap gcc-d.