Arch Linux

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!
Tasklist

FS#79365 - GCC fails to build GCC in Docker

Attached to Project: Arch Linux
Opened by Hugo Sales (someonewithpc) - Saturday, 12 August 2023, 23:45 GMT
Last edited by Toolybird (Toolybird) - Sunday, 13 August 2023, 00:01 GMT
Task Type Bug Report
Category System
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

Building GCC in the attached docker image, based on `archlinux:base-devel` 51879f7f2bef, I get seemingly random compiler crashes. It used to work, about a month ago, but I can't seem to find the image where that was built. When built with `-freport-bug`, I get:

> The bug is not reproducible, so it is likely a hardware or OS problem.

Apologies if this is not the right place to report this.

Additional info:
* archlinux:base-devel 51879f7f2bef
* g++ (GCC) 13.1.1 20230714
* 63fb0bedb8077ac1e6b6337f198b4eae30813fbc gcc commit

Steps to reproduce:

$ docker image build -f Dockerfile.archlinux --tag=gcc-git-arch .
   gcc.log (665 KiB)
   Dockerfile.archlinux (0.5 KiB)
This task depends upon

Closed by  Toolybird (Toolybird)
Sunday, 13 August 2023, 00:01 GMT
Reason for closing:  Not a bug
Additional comments about closing:  See comments
Comment by Hugo Sales (someonewithpc) - Saturday, 12 August 2023, 23:55 GMT
It actually doesn't build in the attached Dockerfile based on Alpine, so it seems like an upstream bug
   Dockerfile.alpine-no-lto (0.6 KiB)
Comment by Toolybird (Toolybird) - Sunday, 13 August 2023, 00:00 GMT
There is no identifiable Arch packaging problem here. Stuff like this belongs in the proper Arch support channels (Forum/IRC/Mailing Lists/Reddit/etc). We are only concerned whether GCC builds properly inside a clean chroot [1] (which it does).

IME, whenever the words "GCC" and "random" are involved, it's pretty much always a hardware issue and/or a problem with your setup.

[1] https://wiki.archlinux.org/title/DeveloperWiki:Building_in_a_clean_chroot

Loading...