Bug 907702

Summary:	sys-devel/gcc-12.2.1_p20230428-r1: bootstrap-prefix.sh stage3 fails (on centos) (OOM)
Product:	Gentoo/Alt	Reporter:	APN-Pucky <alexander>
Component:	Prefix Support	Assignee:	Gentoo Prefix <prefix>
Status:	RESOLVED OBSOLETE
Severity:	normal	CC:	alexander, toolchain
Priority:	Normal
Version:	unspecified
Hardware:	All
OS:	Linux
See Also:	https://bugs.gentoo.org/show_bug.cgi?id=901317 https://bugs.gentoo.org/show_bug.cgi?id=891909
Whiteboard:
Package list:		Runtime testing required:	---
Attachments:	build_stage3_STABLE_generic_centos7_20230602074755.log.xz

Description APN-Pucky 2023-06-02 13:17:31 UTC

System:
Vagrant 2.3.4
generic_centos7 STABLE prefix
Linux centos7.localdomain 3.10.0-1160.88.1.el7.x86_64 #1 SMP Tue Mar 7 15:41:52 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Steps to reproduce the bug:
Run the bootstrap-prefix.sh in mode STABLE (default STABLE) for stage3 (lower ones before)

Error message:

Hmmmm, I was already afraid of this to happen.  Running
  /home/vagrant/gentoo-prefix/bin/bash ./bootstrap-prefix.sh "/home/vagrant/gentoo-prefix" stage3
somewhere failed :(  Details might be found in the build log:
  /home/vagrant/gentoo-prefix/var/tmp/portage/sys-devel/gcc-12.2.1_p20230428-r1/temp/build.log
I have no clue, really.  Please find friendly folks in #gentoo-prefix on
irc.gentoo.org, gentoo-alt@lists.gentoo.org mailing list, or file a bug
at bugs.gentoo.org under Gentoo/Alt, Prefix Support.  This is most
inconvenient, and it crushed my ego.  Sorry, I give up.
Should you want to give it a try, there is /home/vagrant/gentoo-prefix/stage3.log

Extra info:
https://github.com/APN-Pucky/gentoo-prefix-tester/actions/runs/5152480850

Comment 1 APN-Pucky 2023-06-02 13:17:32 UTC

Created attachment 863047 [details]
build_stage3_STABLE_generic_centos7_20230602074755.log.xz

Comment 2 Fabian Groffen gentoo-dev

2023-06-20 09:08:47 UTC

non-RAP succeeds on CentOS 8(.5), RAP fails there too.

Comment 3 Sam James archtester

2024-07-21 17:21:35 UTC

Probably fixed by the various changes mentioned in bug 891909 (not exclusive to LTO).