Date: Fri, 23 Dec 2022 23:41:30 +0900 (JST) From: Yasuhiro Kimura <yasu@FreeBSD.org> To: shoesoft@gmx.net Cc: ports@freebsd.org Subject: Re: nasm-2.16.01,1 build (nearly) locks up machine Message-ID: <20221223.234130.1805506849418287576.yasu@FreeBSD.org> In-Reply-To: <1768153.czEd8160yI@walrus.pepperland> References: <1768153.czEd8160yI@walrus.pepperland>
next in thread | previous in thread | raw e-mail | index | archive | help
From: Stefan Ehmann <shoesoft@gmx.net> Subject: nasm-2.16.01,1 build (nearly) locks up machine Date: Fri, 23 Dec 2022 15:31:00 +0100 > devel/nasm nearly killed my machine today: > > It starts thousands of gmake processes (probably until the machine locks up). > > I also see lots of log entries in the build log (probably ~1 per gmake > invocation): > > : > asm/warnings.time > gmake asm/warnings.c.time include/warnings.h.time doc/warnings.src.time > gmake[13499]: Entering directory '/wrkdirs/usr/ports/devel/nasm/work/ > nasm-2.16.01' > > Seems some kind of make loop. Is this a general problem or is there something > wrong with my setup? I'm building in poudriere on 13.1/amd64. Do you build nasm 2.16.01 with poudriere and you tmpfs for working directory (that is, you specify either 'USE_TMPFS=wrkdir' or 'USE_TMPFS=yes' in poudriere.conf)? If so, you can work it around by disabling use of tmpfs by adding 'USE_TMPFS=no' in poudriere.conf. Bests. --- Yasuhiro Kimura
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20221223.234130.1805506849418287576.yasu>