Porting Pharo VM to another OS

[suhr]

I ported opensmalltalk-vm to Haiku, and would like to port Pharo VM as well. But unlike opensmalltalk-vm, Pharo VM requires working Pharo to compile.

Is there a different way to compile Pharo VM which does not require Pharo on the target OS?

[guillep]

Hi @suhr ! Thanks for the message.

Indeed, porting to a new platform requires bootstrapping from source files, but its not so common for us generally.

You can build from the generated sources, which are stored in https://files.pharo.org/vm/pharo-spur64-headless/Darwin-arm64/source/.
The bundles there (organized by semantic version and commit) contain the entire repo to be build, thus it is standalone, you should be able to build it even without git.
Please ignore the fact that it says "Darwin-arm64", the sources for all platforms and architectures are in the same bundle.

You will need to configure the CMake build with the following options.

https://github.com/pharo-project/pharo-vm/blob/pharo-10/CMakeLists.txt#L28-L29
https://github.com/pharo-project/pharo-vm/blob/pharo-10/CMakeLists.txt#L247

If you wanna try, we can iterate on these instructions and turn them into a wiki page!

index · styled with h5ai 0.22.1 (http://larsjung.de/h5ai/)

index styled with h5ai 0.22.1 (http://larsjung.de/h5ai/)

GitHub

pharo-vm/CMakeLists.txt at pharo-10 · pharo-project/pharo-vm

This is the VM used by Pharo. Contribute to pharo-project/pharo-vm development by creating an account on GitHub.

GitHub

pharo-vm/CMakeLists.txt at pharo-10 · pharo-project/pharo-vm

This is the VM used by Pharo. Contribute to pharo-project/pharo-vm development by creating an account on GitHub.

[suhr]

extracted/vm/scr/unix/aio.c requires Epoll, which is not supported by Haiku.

Before I try to port aio.c to kqueue, I'd like to know one thing. Presumably (judging from cmake files) Pharo VM supports FreeBSD and OpenBSD. But these platforms also use kqueue instead of epoll. How does Pharo VM compile on these platforms?

[guillep]

Well, that's a nice question.

Probably you can take a look at #219 ?

My guess is that epoll changes were introduced after that PR?

And yes, we are not actively building/running on OpenBSD in our CI...

[suhr]

I see, thanks.