Hello Harold, I appreciate the confirmation that the build process should be straightforward. To answer your questions, I've now confirmed the local build issue affects both the master/trunk and the netbsd-11 branches. Here are the host details for the bug report: - Host Distribution: Arch Linux (running a custom kernel/setup) - Host Kernel: Linux 6.17.1-xanmod1-1-edge-x64v3 - Host Compiler: I tested with my system compiler (GCC 14.1.1) and then I downgraded to GCC 9, neither of which resolved the issue. Build Failures Encountered: 1: On master/trunk: Failed during the initial host tool compilation (build_install) due to "incompatible pointer type" errors in texinfo/makeinfo/cmds.c. 2: On netbsd-11: Failed even with BUILD_INSECURE=1 set, during the compilation of the compat library, specifically in strtonum.c. The error was a strictness issue related to the RCSID macro. I haven't yet tested this with other GCC versions yet. I've uploaded the full build log detailing the repeated errors when attempting to build master/trunk to: https://pastee.dev/p/JoaiFUqc I'm still very new to BSD, so I'm unfamiliar with the process for filing a GNATS report or even checking for existing reports. If someone could provide instructions on how to correctly file a report for these I can gather the information and send it along to the proper channel. Regards, DeltaResero ---- On Mon, 20 Oct 2025 02:58:00 -0300 Harold Gutch <logix%foobar.franken.de@localhost> wrote --- > Hi, > > On Sun, Oct 19, 2025 at 09:22:47PM -0300, deltaresero wrote: > > I thought cross compiling it on Linux might have been just as simple as running: > > $ ./build.sh -m evbppc -U tools kernel=WII > > but I kept getting repeated "incompatible pointer type" errors in the texinfo tool's makeinfo/cmds.c file. > > It basically should be, yes. > > Were you trying to build current or netbsd-11? And what host > environment is that on - what Linux distribution/version/architecture > and what compiler (probably gcc - what version?)? > > Or - as you have all the info available anyway, can you perhaps just > open a bug report on https://gnats.netbsd.org ? Basically the > relevant info from up there and the error you're getting. > > > thanks, > Harold >