Hi there,
I’m preparing a new Rebol release (version 3.22.0), and since one syntax change makes it harder to prepare the Haiku version than before, I’d like to know whether anyone is interested in using Rebol on Haiku. Would it be worth investing my time in this task?
Red requires Rebol as a bootstrap, but there is so little activity on Red that even at a glacial pace, Haiku can easily keep up with one rebuild a decade. Their compiler is still 32-bit (AFAIK), adding yet another decade long delay.
Red is using closed sourced Rebol2. And their compiler is not compatible with Rebol3. And I don’t have time to rewrite and maintain their not well documented and still changing compiler’s source code.
My question is, if there is at least any interest in Haiku community to have Rebol scripting language? It is not too difficult to bootstrap a new Haiku build, but as it still requires some work, I take it like a good opportunity to ask this question.
Rebol is a pretty cool language, I played with it back in the day. I’d go as far as to say it helped me learn programming. I don’t use it but I think it would be cool to have it for Haiku, though it would get more traction if it was in HaikuPorts so it shows up in the Haiku apps registry.
I always found REBOL confusing. Syllable decided to use it and it is in my opinion the reason Syllable failed because it polarised development and the dev pushing it is oddly the only one still supposedly doing anything with Syllable these days.
I loved Rebol been available on Beos on times. I think they both share same philosophy. I would be happy to get Rebol under Haiku 
Seems it allreay ported !!! great ! I may give a try to previous release before giving my point btw, still have a book here (old but..)
Ok… so here it is: Release Rebol v3.22.0 · Oldes/Rebol3 · GitHub
Haiku precompiled x86/x64 binaries are available in assets.
Would you mind updating haikuports recipe to bring it up to date with the latest release, checking our current one I see it’s only available for 32bit.
Unfortunately I have zero experience with haikuports.
I’ll try to see if I can get around it today (to make an updated release for the depot), no promises though.
Thanks.. no pressure… I noticed some bugs which I would like to fix, so I will re-release it as 3.22.1 once done.
Guess I have to pass, or search how the build process is done (after first checkout).
EDIT, should be easy with the provided Haiku archives, just extract and copy the command to $prefix/bin
I’m using cross-compilation: Rebol-Docker/haiku/build-rebol-haiku-x64.sh at master · Oldes/Rebol-Docker · GitHub
If compilation on Haiku would be required, there first must be done a bootstrap build, because to compile Rebol one needs Rebol first (many source files are generated).
Here is example of the process for Gentoo.
We @BiPolar and me wrapped up a recipe that pulls in the precompiled binaries, that works too.
If you have an update we’'ll see to update the recipe and put it up on haikuports.
Thanks… you were faster… the release was updated with 3 last minute fixes.
I think you forgot to update the version in the source (still mentions 3.22.0 in Terminal)
PS, in the recipe the binary name is moved to “rebol3”, I hope that’s OK?
EDIT: my bad on the version, still had the previous version in my download folder, all good now! 
EDIT2: @Oldes is the 32bit version build with gcc13 or gcc2? This makes a difference on the requirements in the recipe. (haiku and libiconv)
I’m using 32bit version of Rebol on Haiku.
I’ve checked a package created here for 32bit, that woks well, I’m just not sure yet if it requires /system/lib/libiconv or /system/lib/x86/libiconv on 32bit (granted didn’t check with readelf -d there).
