From what I've gathered the OpenBSD project does all of their builds on the native hw, as opposed to using crosscompiles. This ensures the hw port actually work

From what I've gathered the OpenBSD project does all of their builds on the native hw, as opposed to using crosscompiles. This ensures the hw port actually works and also validates code in general. For example sparc(64) requires strict pointer alignement and is big endian. Code that fails because of those architectural differences may have other problems. Looking forward maybe static analysis diminishes the utility of this practice. Anyway I was a latecomer to vax. My first one was a 4000 VLC I bought off ebay to mess around with when I was in highschool in the early 2000s. I ran openbsd on it and used it as a dns server for a while. My mom later threw it out while I was away at college, along with a perfectly fine indy. Oh well I should have know better. Anyway it's sad to see it go but if no one is stepping up to do the work or there isn't any hardware to run it on, dropping it makes sense for the project. Also OpenBSD has been using a very old version of gcc for the same reason OSX uses an old version of bash: GPLv3. The future of OpenBSD probably lies with LLVM so any architectures which don't have solid llvm targets are probably doomed as well.[0] [0] I just noticed someone on the list made a similar observation: https://marc.info/?l=openbsd-misc&m=145375994431577&w=2 https://marc.info/?l=openbsd-misc&m=145375994431577&w=2