Date: Thu, 30 Jun 2022 00:53:21 +0000 From: bugzilla-noreply@freebsd.org To: toolchain@FreeBSD.org Subject: [Bug 264949] lang/gcc11: Needs build time warning for /tmp consumption Message-ID: <bug-264949-29464-VG3GuiShmD@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-264949-29464@https.bugs.freebsd.org/bugzilla/> References: <bug-264949-29464@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D264949 --- Comment #12 from Mark Millard <marklmi26-fbsd@yahoo.com> --- (In reply to Lorenzo Salvadore from comment #11) FreeBSD's port build servers are not used for native armv7 or armv6 build activity: qemu is used instead. lang/gcc* have the issue that the after the system clang built stage, the rest of the stages no longer use system clang to cross compile: just qemu. (armv7 and armv6 also have address space limitations in contexts were the hardware can directly execute the code, not that official builds use such hardware.) LTO_BOOTSTRAP based builds targeting for armv7/armv6 never worked on those builders as I understand. The disabling of LTO_BOOTSTRAP style for armv7/armv6 was to allow the FreeBSD servers to finally manage to build the lang/gcc* armv7/armv6 ports that had tried to use LTO_BOOTSTRAP for armv7/armv6. (There is more to the story for what alternative was selected as I understand, but that is not relevant here.) As always, the default OPTIONS are the definition of what the official port build servers build --and those definitions are not based on what people who choose to do their own builds select for OPTIONS. (Note: I build my own.) The OPTIONS allow avoiding the LTO bootstrap. (And I do avoid LTO_BOOTSTRAP .) --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-264949-29464-VG3GuiShmD>