Back

And then, I went and finally pushed my epoll reworking over the finish line — there was not that much work left, but it had to be done. Once it was, everything fell into place, and now long polls work, short polls work, polls with no interests (basically using epoll as a sleep) work, signals work (including pwait and pwait2 atomically changing the signal mask), and everything seems to just work.

Also apparently my epoll is going into the Hurd upstream soon? Exciting!

Next, I took my "portable" Wayland patchset and rebased it onto latest upstream main. It's both better and worse; the upstream have done some BSD portability work, so equivalents of some of my changes have effectively been upstreamed, but also they added eventfd usage, so, yay, more things to patch out.

Anyway, so I got Wayland building on the Hurd once again. The tests don't yet pass, I'll need to look into that tomorrow.

After that: Owl, and gtk with its Wayland backend.

wl-clipboard, Owl

There we go!

This is Weston's demo clients again — being built with a lot less hacks this time.

It would certainly help if they all didn't just

#include <linux/input.h>

And this is gtk4

@bugaevc watching the Hurd become more functional is nice

@bugaevc I would help but I have my own wild OS projects

@bugaevc if I knew more about LLVM internals I might attempt to do Rust to it but that sounds scary tbh

@alilly @bugaevc Rust does seem like a very appropriate language to rewrite LLVM in. Given the hacks LLVM wrote to get pattern-matching...

Also GHC shows that pattern-matching is very handy for this task!

@alcinnz @bugaevc slight non sequitor but okay