Date: Fri, 23 Dec 2022 19:31:35 +0000 From: Lorenzo Salvadore <developer@lorenzosalvadore.it> To: ports@freebsd.org Subject: Re: nasm-2.16.01,1 build (nearly) locks up machine Message-ID: <wnM_xzwrtkiaDkmnlKjpdf88Lx-BsQcAt8jn-y1ycx3JmpAFw3FpzjEqeARZkR4a1eKWiTbSPciJAHgDPx46z8cLMn4S3oqzy9FhWOhjqaQ=@lorenzosalvadore.it> In-Reply-To: <t9vDJg48VysJFsYezPNiv5RpOlVCx6jNA3Pt_D3r4BQ4UTM9An153YpbAFO1pVY33vF-WUpbGnG8KrHhO-CSDjWBP450LpclwHpLz7A0Iow=@lorenzosalvadore.it> 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> <t9vDJg48VysJFsYezPNiv5RpOlVCx6jNA3Pt_D3r4BQ4UTM9An153YpbAFO1pVY33vF-WUpbGnG8KrHhO-CSDjWBP450LpclwHpLz7A0Iow=@lorenzosalvadore.it>
next in thread | previous in thread | raw e-mail | index | archive | help
------- 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?wnM_xzwrtkiaDkmnlKjpdf88Lx-BsQcAt8jn-y1ycx3JmpAFw3FpzjEqeARZkR4a1eKWiTbSPciJAHgDPx46z8cLMn4S3oqzy9FhWOhjqaQ=>