Date: Wed, 29 Jun 2022 13:59:05 +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-lHEhjtn2Oo@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 Mark Millard <marklmi26-fbsd@yahoo.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |marklmi26-fbsd@yahoo.com --- Comment #4 from Mark Millard <marklmi26-fbsd@yahoo.com> --- (In reply to Lorenzo Salvadore from comment #1) poudriere(-devel) based build? If so, what USE_TMPFS in /usr/local/etc/poudriere.conf ? I'll note that if USE_TMPFS includes workdir (for example, for "yes"), something like rust can use 20+ GiBytes of tmpfs. The cited change in how rust was ma= de to work does not generally solve the problem that it was trying to solve, just= for a limited range of styles of builds. poudriere.conf also has: # List of package globs that are not allowed to use tmpfs for their WRKDIR # Note that you *must* set TMPFS_BLACKLIST_TMPDIR # EXAMPLE: TMPFS_BLACKLIST=3D"rust" The TMPFS_BLACKLIST_TMPDIR place needs sufficient free disk space, even th= ough this avoids RAM+SWAP being needed. I avoid large tmpfs use by poudriere bulk runs via using USE_TMPFS=3D"data". --=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-lHEhjtn2Oo>