Phase 2 took a step forward. Someone else fixed a threading issue and that made everything pass on the HEAD of the git repository for #Chez #scheme on my #haikuos build box. So I've just submitted the PR to the upstream project to re-establish Haiku support in Chez. Let's see how that goes.
Reminder, the #haikuports version of Chez Scheme is already available.
I've done a bit of experimenting getting #racket to build, but I'm not there yet. #Akku looks promising too.
The #chez #scheme port got merged in the #haikuports repository just under an hour ago.
Yay. Happy hacking #haikuos users who love Scheme (there must be at least four of us!).
Well, I had to learn more that I was expecting (particularly about how tests work in the #chez #scheme code), but I've just submitted the PR on the #haikuports
repository. If that port gets accepted I'll have a go at getting the new #haiku machine types for Chez added to the upstream project.
I might then move towards getting #racket up and running on #Haiku on the basis of the Chez port. #haikuos
A little update on my efforts to port #chez #scheme to #Haikuos . I'm pretty sure (as per my last post) that its running fine, but there are certain aspects of Haiku that need to be properly reflected in the test suite.
Chief among these areas is the filesystem - some file operations that the test suite expects to fail, which simply succeed. Some of this is because Haiku, as a single-user OS, basically gives you root rights across the whole filesystem.