Why is (nb)ctfmerge failing when linking larger kernels???

"Greg A. Woods" <[email protected]>
Newsgroups gmane.os.netbsd.current,gmane.os.netbsd.ports.x86-64
Organization Planix, Inc.
Message-ID <[email protected]>
At Wed, 01 Jul 2020 17:57:08 -0700, "Greg A. Woods" <[email protected]> wrote:
Subject: weird occasional "Resource exhaustion" errors when linking GENERIC_KASLR
>
> I've been using a stock 9.0 amd64 install to build my -current tree and
> found it failing with a "Resource exhaustion" error (also "Out of
> memory") when linking the GENERIC_KASLR kernel.

So even in 9.99.64 ctfmerge fails, especially with the ALL kernel
(though I must admit I haven't tried to build an amd64 ALL kernel for
perhaps a year or so):

       link  ALL/netbsd
NetBSD 9.99.64 (ALL) #0: Thu Jul  2 17:29:25 PDT 2020
   text    data     bss     dec     hex filename
80120264        174291832       8122368 262534464       fa5f540 netbsd
ERROR: nbctfmerge: netbsd.ctf: Cannot finalize temp file: Resource exhaustion: Cannot allocate memory
--- netbsd ---
*** [netbsd] Error code 1

nbmake: stopped in /build/woods/xentastic/current-amd64-amd64-obj/build/src-current/sys/arch/amd64/compile/ALL
1 error

$ ulimit -a
time(cpu-seconds)    unlimited
file(blocks)         unlimited
coredump(blocks)     unlimited
data(kbytes)         8388608
stack(kbytes)        32768
lockedmem(kbytes)    512000
memory(kbytes)       4096000
nofiles(descriptors) 3404
processes            420
threads              2048
vmemory(kbytes)      2097152
sbsize(bytes)        unlimited

--
					Greg A. Woods <[email protected]>

Kelowna, BC     +1 250 762-7675           RoboHack <[email protected]>
Planix, Inc. <[email protected]>     Avoncote Farms <[email protected]>
signature.asc (application/pgp-signature, 195 B)
-----BEGIN PGP SIGNATURE-----

iF0EABECAB0WIQRuK6dmwVAucmRxuh9mfXG3eL/0fwUCXwEGNgAKCRBmfXG3eL/0
f0ViAJ97LcsdUi8RGLNC/2n69/5MIqUlAgCgus1Eeg768NP8p1PuL6xhlwdhyzc=
=edBN
-----END PGP SIGNATURE-----
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.