Re: Building NetBSD 11 Release from Source Fails on Linux/MacOS

[Helge Pfeiffer <ropf%itu.dk@localhost>]

On Fri, 2026-11-13 at 08:41 +0000, RVP wrote:
> On Thu, 12 Nov 2026, Helge Pfeiffer wrote:
> 
> > Thank you very much for doing that! I wonder: When
> > installing
> > physically, did you choose to enable disk encryption?
> > 
> 
> I didn't actually install Pop!_OS 24.04 onto a disk. Just
> clicked on the
> "Try Demo Mode", and that's not likely to be encrypted, I
> think.
> 
I see. And this worked for you but not for me. Neither with
encrypted nor "plain" filesystem... weird.

> > The tar archive contains nine files, three per OS. Per
> > OS,
> > there is one gzipped log of building the toolchain
> > (parallel
> > built), which I only include for completeness (perhaps it
> > is
> > irrelevant, but I think it illustrates that nbm4 is
> > already
> > used in that build without any issue). Then, there is a
> > file
> > with gzipped release build logs (built with -j1). Lastly,
> > there is a plain text file (.host_info) that lists some
> > of
> > the environment information like compiler, linker, stdlib
> > versions, etc.
> > 
> 
> 1. I see that you have an older kernel on the same Pop!_OS
> 24.04:
> 
> ```
> ===> Build platform:      Linux 6.18.7-76061807-generic
> x86_64
> ```
> 
>    whereas I get:
> 
> ```
> ===> Build platform:      Linux 7.0.11-76070011-generic
> x86_64
> ```
> 
>    Looks like they've updated the packages in the latest
> .iso file.
Yes, this is true. However, I have the same issue with this
kernel too. That was the fresh install that I mentioned in my
last message. (I do not include the build logs nor obj dir
for this one in the linked archive though.

> 
> 2. Can you tar(1) up the entire ~/obj dir. after
> `./build.sh ... tools release'
>     fails, and upload that somewhere? (Make sure to wipe
> ~/obj first.)
There is a tar archive here:
https://ituniversity-my.sharepoint.com/:u:/g/personal/ropf_itu_dk/IQCQD93KkMU_QZ3AuJC22P0IAcaCNVM8ZHKlxffmjJyHP-U?e=2Av717


It contains all the files described in my last message, plus
per OS, an xz compressed archive (with the name of the
respective OS) that contains the compressed obj dir.

I am sending the complete bundle again, to be sure to have
the correct log files for the obj dir per build. Since I
already deleted everything on MacOS Sequoia after my last
message, I recreated everything for the build on it. That is,
it is likely best to disregard the link from my last message
and just use the link above.
> 
> Thx,
Thanks to you for looking into this!
> 
> -RVP

Best,
Helge