Arch Linux

Please read this before reporting a bug:

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
Task Type Bug Report
Category Packages: Core
Status Assigned
Assigned To Giancarlo Razzolini (grazzolini)
freswa (frederik)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 0
Private No


gcc-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

Comment by Allan McRae (Allan) - Tuesday, 22 March 2022, 07:24 GMT
Looking at the package, it is the go and d language source files. The distro makepkg needs backports to support languages other than C or C++...
Comment by Toolybird (Toolybird) - Tuesday, 22 March 2022, 07:26 GMT
(edit: Allan beat me to the punch :)

Looking deeper, this is likely a pacman issue, and it might already be fixed by:

Comment by Allan McRae (Allan) - Tuesday, 22 March 2022, 07:47 GMT
Or we could drop gcc-go and gcc-d... No-one needs these anyway :)
Comment by Toolybird (Toolybird) - Tuesday, 22 March 2022, 07:53 GMT
Funny you should say that.. I've been working on some bootstrapping issues and guess where the pain points are?

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.