Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 23 Dec 2022 15:48:21 +0100
From:      Stefan Ehmann <shoesoft@gmx.net>
To:        ports@freebsd.org, Yasuhiro Kimura <yasu@freebsd.org>
Subject:   Re: nasm-2.16.01,1 build (nearly) locks up machine
Message-ID:  <5425790.xR3xz5vsG8@walrus.pepperland>
In-Reply-To: <20221223.234130.1805506849418287576.yasu@FreeBSD.org>
References:  <1768153.czEd8160yI@walrus.pepperland> <20221223.234130.1805506849418287576.yasu@FreeBSD.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On Friday, December 23, 2022 3:41:30 PM CET Yasuhiro Kimura wrote:
> 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 loc=
ks
> > 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.tim=
e
> > 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=3Dwrkdir' or
> 'USE_TMPFS=3Dyes' in poudriere.conf)?
>
> If so, you can work it around by disabling use of tmpfs by adding
> 'USE_TMPFS=3Dno' in poudriere.conf.

Yea, I have USE_TMPFS=3Dall in poudriere.conf. USE_TMPFS=3Dno works indeed=
.

Thanks for the fast reply.





Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5425790.xR3xz5vsG8>