> On Aug 8, 2025, at 15:31, Greg Troxel <g...@lexort.com> wrote: > > zamfofex <zamfo...@twdb.moe> writes: > >>> I have a Pentium II 350 machine that I run NetBSD 10.1 on. Obviously, it >>> can build for itself, especially since it has a silly 1GB of RAM, but it’s >>> extremely slow, as expected, when building. >>> >>> So, I use an AMD64 VM , also running NetBSD 10.1, to do the building. I’m >>> having issues cross-compiling GCC12, and wanted to see if anyone else has >>> seen the same issue. > > > I think it's great that you are trying cross compiling and raising > issues. I think cross is great in general. > >> 2) Install i386 NetBSD on your build machine. >> >> To avoid the issue of having to cross-compile packages altogether, you could >> install NetBSD for i386 on your build machine (either natively or on a VM) >> and build the packages that way. >> >> It should be possible to run NetBSD for i386 on AMD64 hardware (on bare >> metal, but also on a VM running on either i386 or AMD64 host OS with working >> CPU-accelarated virtualisation). >> >> Since you say that the package(s) you want wouldn’t take more than 1GB to >> build, it should be fine on 32-bit address space. > > This is also great advice. I have a modern adm64 box running xen and I > have domUs for netbsd 9, 10, 11 i386 and amd64 (but not 11-i386) to > build packages.
Thanks for the suggestions. I am indeed aware that I can use pkgin to install binary packages, and I do that sometimes, but I generally prefer to build my own packages, to make sure that they still are capable of being built in all situations. Also, I indeed can run NetBSD i386 on a VM, but as you know, that limits the amount of RAM available for building, given the limits of PAE. I did, by the way, use build.sh to build the cross-compiling tools. I have successfully built a number of packages already: $ ls -l /usr/pkgsrc/packages.NetBSD-10.1-i386/All/ total 64640 -rw-r--r-- 1 root 125 3199291 Aug 7 23:40 bash-5.2.37.tgz -rw-r--r-- 1 root 125 19297168 Aug 7 22:55 perl-5.40.2nb1.tgz -rw-r--r-- 1 root 125 1776962 Aug 7 23:39 vim-9.1.1572.tgz -rw-r--r-- 1 root 125 8731683 Aug 7 23:38 vim-share-9.1.1572.tgz I’d like to figure out what the issue with GCC 12 is, as I think that it may be cross-compile specific, given this report, on a different platform, that got the same error: https://issues.guix.gnu.org/55665 Thanks! - Alex
