From nobody Fri Dec 23 18:26:30 2022 X-Original-To: ports@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4Ndwcf5yXDz1HKlv for ; Fri, 23 Dec 2022 18:26:42 +0000 (UTC) (envelope-from junchoon@dec.sakura.ne.jp) Received: from www121.sakura.ne.jp (www121.sakura.ne.jp [153.125.133.21]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4Ndwcd1TKTz4PPX for ; Fri, 23 Dec 2022 18:26:40 +0000 (UTC) (envelope-from junchoon@dec.sakura.ne.jp) Authentication-Results: mx1.freebsd.org; dkim=none; spf=none (mx1.freebsd.org: domain of junchoon@dec.sakura.ne.jp has no SPF policy when checking 153.125.133.21) smtp.mailfrom=junchoon@dec.sakura.ne.jp; dmarc=none Received: from kalamity.joker.local (123-1-88-210.area1b.commufa.jp [123.1.88.210]) (authenticated bits=0) by www121.sakura.ne.jp (8.16.1/8.16.1/[SAKURA-WEB]/20201212) with ESMTPA id 2BNIQUei062904 for ; Sat, 24 Dec 2022 03:26:30 +0900 (JST) (envelope-from junchoon@dec.sakura.ne.jp) Date: Sat, 24 Dec 2022 03:26:30 +0900 From: Tomoaki AOKI To: ports@freebsd.org Subject: Re: nasm-2.16.01,1 build (nearly) locks up machine Message-Id: <20221224032630.8bba7b7b246f20450e16f22f@dec.sakura.ne.jp> In-Reply-To: <5425790.xR3xz5vsG8@walrus.pepperland> References: <1768153.czEd8160yI@walrus.pepperland> <20221223.234130.1805506849418287576.yasu@FreeBSD.org> <5425790.xR3xz5vsG8@walrus.pepperland> Organization: Junchoon corps X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.33; amd64-portbld-freebsd13.0) List-Id: Porting software to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-ports List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-ports@freebsd.org X-BeenThere: freebsd-ports@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Spamd-Result: default: False [-1.59 / 15.00]; AUTH_NA(1.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.99)[-0.990]; MV_CASE(0.50)[]; MIME_GOOD(-0.10)[text/plain]; R_DKIM_NA(0.00)[]; ASN(0.00)[asn:7684, ipnet:153.125.128.0/18, country:JP]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; R_SPF_NA(0.00)[no SPF record]; MLMMJ_DEST(0.00)[ports@freebsd.org]; RCVD_TLS_LAST(0.00)[]; HAS_ORG_HEADER(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; FROM_HAS_DN(0.00)[]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; DMARC_NA(0.00)[sakura.ne.jp]; TO_MATCH_ENVRCPT_ALL(0.00)[]; TO_DN_NONE(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[ports@freebsd.org]; RCPT_COUNT_ONE(0.00)[1]; MID_RHS_MATCH_FROM(0.00)[] X-Rspamd-Queue-Id: 4Ndwcd1TKTz4PPX X-Spamd-Bar: - X-ThisMailContainsUnwantedMimeParts: N On Fri, 23 Dec 2022 15:48:21 +0100 Stefan Ehmann wrote: > On Friday, December 23, 2022 3:41:30 PM CET Yasuhiro Kimura wrote: > > From: Stefan Ehmann > > 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. > > Yea, I have USE_TMPFS=all in poudriere.conf. USE_TMPFS=no works indeed. > > Thanks for the fast reply. I've bitten by it, too. Found this. [1] [2] [2] is linked from [1]. But Not at all tried though (as I'm not sure it is safe [100% upper compatible] to switch to -devel). ports-mgmt/poudriere-devel seems to have it, but ports-mgmt/poudriere doesn't. [1] https://github.com/freebsd/poudriere/issues/888 [2] https://github.com/freebsd/poudriere/commit/56233a1aaea1be59dcc111e7b3f97b6e891bb06a -- Tomoaki AOKI