Hi,
On Fri, Oct 17, 2025 at 09:21:06PM -0700, Mark Millard wrote:
At this point stable/15 and a non-debug main 16 are not all that
different. So I attempted builds of what I had for a ports tree
(from Oct 13) and then updating the ports tree and rebuilding
what changed ( PKG_NO_VERSION_FOR_DEPS=yes style ) based on my
normal environment and poudriere-devel use.
Neither failed.
But you give little configuration information so I do not
know how well my attempt approximated your context:
Point taken but at that stage I only wanted to know if others
could build it, because I couldnt on multiple poudrieres and
it had/has not yet (2025.10.18-1224 UTC) been built on the pkg cluster.
Now that I know it can be built, I partially know where to look, and
I avoid making a PR for the port.
RAM+SWAP == ??? + ??? == ???
128+4 == 132GB
The problem happened on two systems. For simplicity I'm talking about the
beefier system. It has 20 cpu (40 with HT on but it is turned off)
and 128GB ram. configured swap is 4GB and hardly used.
poudriere.conf :
USE_TMPFS=???
all
TMPFS_BLACKLIST=???
not defined
PARALLEL_JOBS=??? # (or command line control of such)
1 in poudriere.conf at the moment. It usually has 3 as per pkg.f.o
but -J20 was also tried directly on the command line
ALLOW_MAKE_JOBS=??? # (defined vs. not)
yes
ALLOW_MAKE_JOBS_PACKAGES=???
undefined
MUTUALLY_EXCLUSIVE_BUILD_PACKAGES=???
"llvm* rust* gcc*"
PRIORITY_BOOST=???
undefined
other relevant possibilities?
make.conf (or command line control of such):
MAKE_JOBS_NUMBER_LIMIT=??? # or MAKE_JOBS_NUMBER=???
not defined within jailname-make.conf
Details for my context . . .
Thank you for your time in this. I'm interested - do you
make available your hacked version of top? Could be useful!
--
