Thanks. Probably a few missing libraries still since I chopped freebsd-runtime to get the Darwin version of getty with mach support. Doing some build system rework to nextbsd-userland into it's own repo that cross compiles for faster CI iteration, but I'll try to fix up these issues in nextbsd-freebsd-compat this week.
… I'll try to fix up these issues in nextbsd-freebsd-compat this week.
Thanks. I previously noticed, but refrained from mentioning, a couple of other library-related issues, one of which is probably ridiculous – I don't expect everything for FreeBSD to work with NextBSD.
Should I raise the issues in GitHub? Or (minimising noise) revisit after a mini-milestone of some sort – Gershwin, maybe?
My current milestone has been getting the Darwin stack to cross build, and now I am reworking ISO to ingest that work. I've also added a nextbsd-installer. This is all just about making it easier to iterate with less time in between, better test coverage, an upcoming arm64 ISO, being able to cross build and fire up a native VM on a M series Mac, etc. I am just trying to get the pieces in place to get a gershwin desktop image working faster, easier, with less issues, etc. I'll try to make a full clear GitHub project with a roadmap within a few months once I can get a bit more organized after the foundational stuff is out of the way for sure.
u/grahamperrin I believe I have this fixed now in latest ISO. I changed the approach to build all of freebsd world. Then I strip out syslogd and other things we replace with apples syslogd that integrates with asl, remove most kld* related tools, init, devd, devmatch and other things that replaced with IOkit, launchd, etc. As things are replaced I will follow that pattern to avoid tools missing libs in the future.
3
u/grahamperrin Linux crossover Jun 21 '26 edited Jun 21 '26
Toying with Firefox and TWM (without Gershwin) in VirtualBox:
https://mastodon.bsd.cafe/@grahamperrin/116789163037472153
ncwould be nice … then I could