Re: Building packages - qemu vs. CC etc.
Martin Husemann <[email protected]> Wed, 3 Jun 2026 09:38:02 +0200
| Newsgroups | gmane.os.netbsd.ports.sparc |
|---|---|
| Message-ID | <[email protected]> |
On Tue, Jun 02, 2026 at 08:03:04PM -0400, Mouse wrote: > > (Possible dumb question - any advantage to CCâ??ing on a sparc64 (v240 / 4G $ > > "Maybe." Yes, sparc64 and sparc are closely related; most (all?) > sparc64 hardware can run sparc32 userland binaries just fine, provided > the kernel is prepared to support it, which I think NetBSD/sparc64 is > if your kernel includes sparc32 compat - or at least it's supposed to > be; I can't recall trying it myself. The sparc64 GENERIC kernel can run 32bit sparc userland. There are some gaps in the 32bit emulation (in general, not sparc/sparc64 specific) and there are some unclear issues with sparc libpthread, where it is unclear if we hit the issues just because the hardware is faster and sparc libpthread is broken, or something else is going on. That is the reason this combination is not part of my weekly test runs (the ATF test run just never completes w/o manual intervention). There are weekly runs for i386 on amd64: https://www.netbsd.org/~martin/amd64-compat32-atf/ and evbarm7hf-el on aarch64: https://www.netbsd.org/~martin/aarch64-compat32-atf/ which both show more test failures than the native counterparts (e.g. https://www.netbsd.org/~martin/evbearmv7hf-atf/). Martin