From nobody Fri Dec 23 19:31:35 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 4Ndy3c6Rw9z1HV0F for ; Fri, 23 Dec 2022 19:31:40 +0000 (UTC) (envelope-from developer@lorenzosalvadore.it) Received: from mail-4018.proton.ch (mail-4018.proton.ch [185.70.40.18]) (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-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "protonmail.com", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Ndy3c1pqGz3hTx for ; Fri, 23 Dec 2022 19:31:40 +0000 (UTC) (envelope-from developer@lorenzosalvadore.it) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=lorenzosalvadore.it header.s=protonmail header.b="p7/xK7hv"; spf=pass (mx1.freebsd.org: domain of developer@lorenzosalvadore.it designates 185.70.40.18 as permitted sender) smtp.mailfrom=developer@lorenzosalvadore.it; dmarc=pass (policy=quarantine) header.from=lorenzosalvadore.it Date: Fri, 23 Dec 2022 19:31:35 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=lorenzosalvadore.it; s=protonmail; t=1671823898; x=1672083098; bh=tBQ4Q3IxPdwBEIBodQiOzH0vCuxhPTCf4APxQVXmDNY=; h=Date:To:From:Subject:Message-ID:In-Reply-To:References: Feedback-ID:From:To:Cc:Date:Subject:Reply-To:Feedback-ID: Message-ID:BIMI-Selector; b=p7/xK7hveAvd3JdOkH28MIlPgqRnFRWeWOgwOq71ep5eWWHj7SCmX8mLD03HfWAjG rrujKlsVbZRJ/kKQajaqwl0tWKgLwQq5PmHQ29yPkgITbxe9I3Gyx15Gu4LhM24rlH VQ69OHH9gkVC3gd2xtfvTO3HD9RxpJa24BjnZQX8DL2hKREQS55ZxcG6REPHJrdsK4 cG4UgLQJZhtNRZKlpvIuFdXu2Er1vG+qlf+VyZGLtHNMZDC4aemzZjqGOC/gQKDcl8 +8v32gXguEZ5BAOYhHrJ7ppH1K9Lx1stY9u9g7DQ9h179gIPNYxAevQ1Csn903kGCU AzptPpsTdftOg== To: ports@freebsd.org From: Lorenzo Salvadore Subject: Re: nasm-2.16.01,1 build (nearly) locks up machine Message-ID: In-Reply-To: References: <1768153.czEd8160yI@walrus.pepperland> <5425790.xR3xz5vsG8@walrus.pepperland> <20221224032630.8bba7b7b246f20450e16f22f@dec.sakura.ne.jp> <1752738.OGYTO6zm24@walrus.pepperland> <20221224041841.a13750c9c862c349c980738a@dec.sakura.ne.jp> Feedback-ID: 53711648:user:proton 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=utf-8 Content-Transfer-Encoding: quoted-printable X-Spamd-Result: default: False [-3.94 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.98)[-0.983]; NEURAL_HAM_LONG(-0.96)[-0.959]; DMARC_POLICY_ALLOW(-0.50)[lorenzosalvadore.it,quarantine]; R_SPF_ALLOW(-0.20)[+ip4:185.70.40.0/24:c]; R_DKIM_ALLOW(-0.20)[lorenzosalvadore.it:s=protonmail]; MIME_GOOD(-0.10)[text/plain]; MLMMJ_DEST(0.00)[ports@freebsd.org]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; RCVD_COUNT_ZERO(0.00)[0]; ARC_NA(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; ASN(0.00)[asn:62371, ipnet:185.70.40.0/24, country:CH]; FROM_HAS_DN(0.00)[]; DKIM_TRACE(0.00)[lorenzosalvadore.it:+]; TO_MATCH_ENVRCPT_ALL(0.00)[]; TO_DN_NONE(0.00)[]; MID_RHS_MATCH_FROM(0.00)[] X-Rspamd-Queue-Id: 4Ndy3c1pqGz3hTx X-Spamd-Bar: --- X-ThisMailContainsUnwantedMimeParts: N ------- Original Message ------- On Friday, December 23rd, 2022 at 8:18 PM, Tomoaki AOKI junchoon@dec.sakura= .ne.jp wrote: > On Fri, 23 Dec 2022 19:50:55 +0100 > Stefan Ehmann shoesoft@gmx.net wrote: >=20 > > On Friday, December 23, 2022 7:26:30 PM CET Tomoaki AOKI wrote: > >=20 > > On Fri, 23 Dec 2022 15:48:21 +0100 > > >=20 > > > Stefan Ehmann shoesoft@gmx.net wrote: > > >=20 > > > > On Friday, December 23, 2022 3:41:30 PM CET Yasuhiro Kimura wrote: > > > >=20 > > > > > 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 > > > > >=20 > > > > > > devel/nasm nearly killed my machine today: > > > > > >=20 > > > > > > It starts thousands of gmake processes (probably until the mach= ine > > > > > > locks > > > > > > up). > > > > > >=20 > > > > > > I also see lots of log entries in the build log (probably ~1 pe= r gmake > > > > > >=20 > > > > > > invocation): > > > > > > : > asm/warnings.time > > > > > >=20 > > > > > > 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' > > > > > >=20 > > > > > > Seems some kind of make loop. Is this a general problem or is t= here > > > > > > something wrong with my setup? I'm building in poudriere on > > > > > > 13.1/amd64. > > > > >=20 > > > > > Do you build nasm 2.16.01 with poudriere and you tmpfs for workin= g > > > > > directory (that is, you specify either 'USE_TMPFS=3Dwrkdir' or > > > > > 'USE_TMPFS=3Dyes' in poudriere.conf)? > > > > >=20 > > > > > If so, you can work it around by disabling use of tmpfs by adding > > > > > 'USE_TMPFS=3Dno' in poudriere.conf. > > > >=20 > > > > Yea, I have USE_TMPFS=3Dall in poudriere.conf. USE_TMPFS=3Dno works= indeed. > > > >=20 > > > > Thanks for the fast reply. > > >=20 > > > I've bitten by it, too. > > > Found this. [1] [2] > > > [2] is linked from [1]. > > >=20 > > > But Not at all tried though (as I'm not sure it is safe [100% upper > > > compatible] to switch to -devel). > > >=20 > > > ports-mgmt/poudriere-devel seems to have it, but ports-mgmt/poudriere > > > doesn't. > > >=20 > > > [1] https://github.com/freebsd/poudriere/issues/888 > > >=20 > > > [2] > > > https://github.com/freebsd/poudriere/commit/56233a1aaea1be59dcc111e7b= 3f97b6e > > > 891bb06a > >=20 > > Thanks for the pointer. The rust tmpfs problem is different - it will w= ork if > > you have enough RAM. For some reason (not obvious to me), nasm build is > > totally broken on tmpfs. > >=20 > > Meanwhile, the nasm update was reverted in commit > > 102f7173426ac4122afd355205aa141bb50b2803. >=20 > The most important thing is that [2] introduced TMPFS_BLACKLIST > variable. >=20 > I think adding nasm there causes building nasm without using tmpfs, > while other ports, excluding listed there at the same time, can keep on > using tmpfs. >=20 > P.S. > To test pre-built nasm causes failure on ports BUILD_DEPENDing on nasm, > I've done below and confirmed OK, even with USE_TMPFS=3Dyes > on /usr/local/etc/poudriere.conf. > So maybe TMPFS_BLACKLIST'ing nasm alone would be sufficient. >=20 > 1. Built devel/nasm with ports-mgmt/pkg_replace, which builds fine, > 2. pkg create it, > 3. start usual poudriere run with unusual "-i" added, > 4. after poudriere goes into shell, copy pre-built nasm package, > to /poudriere/data/packages/(jain name)/All/, > 5. exit shell invoked by poudriere, > 6. once finished, delete jpeg-turbo package from > /poudriere/data/packages/(jain name)/All/, > 7. build jpeg-turbo using poudriere. >=20 > Copying pre-build nasm package without steps 3-5 caused re-building > nasm, which promissingly fails. Thank you very much for reporting the issue. As it has already been noted, the commit that broke nasm has been reverted = with https://cgit.freebsd.org/ports/commit/?id=3D102f7173426ac4122afd355205aa141= bb50b2803 . =20 Investigations have started to understand the issue and a bug report has be= en opened to track the issue: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D268528 Thanks and sorry for the broken update, Lorenzo Salvadore