Date: Wed, 29 Jun 2022 11:54:48 +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@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D264949 Bug ID: 264949 Summary: lang/gcc11: Needs build time warning for /tmp consumption Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: Individual Port(s) Assignee: toolchain@FreeBSD.org Reporter: junchoon@dec.sakura.ne.jp Assignee: toolchain@FreeBSD.org Flags: maintainer-feedback?(toolchain@FreeBSD.org) lang/gcc11 is now the default version of gcc at ports git cad2f66a384d74cffa870d978722e6fd579c7d2f. On updating, build exhausted by insufficient capacity of /tmp. At the moment, I had 2GiB of tmpfs for /tmp, backed with 32GiB swap. stable13 at git dac438a9b599cfec13b463a1a8d90283f7ed830f, amd64. By increasing /tmp with 1GiB step (with reboots), finally build finished successfully with 5GiB of/tmp. (4GiB was insufficient.) I'm not sure this is really reasonable for just a toolchain though, at leas= t, this SHALL be warned like www/chromium does on pre-everything:: target does. Is this because of LTO_BOOTSTRAP option (default of amd64)? Note that /tmp was used only 1.7MiB after building lang/gcc11 finished and lang/gcc10 with default option was OK with 2GiB of /tmp. --=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>