Wolfgang Thaller

I actually forgot to mention that :-). I have a first version of this working (commit 7e465e30f1e509ac9b10f7060055d9378a8d7092), but I don't quite trust it yet. I'm not sure if I've actually...

Another thing that needs deciding is what to do about the Mac frontend; I've removed the mac-specific frontend from my fork because I think it contains too much ancient NeXT-specific...

I've started a wiki page at https://github.com/ctm/executor/wiki/Plans---TODO where I listed a lot of ideas that I want to do / think that should be done / would be cool to...

If what you want to learn is related to my Executor 2000 fork, you can head over there (https://github.com/autc04/executor) and either ask a question publicly on github or write to...

You are probably right in that preference should have been give to the BSD headers. I am also now thinking - maybe the headers could be patched with some preprocessor...

I'm excited about the idea of a BeOS port. I have one old Mac capable of running BeOS/PPC, though I've been too busy with other things (= lazy) to do...

Yes. When called with these switches, the Retro68 gcc should skip all the mac-specific libraries.

I'm guessing that the first step would be to get something *without* setup code to work, i.e. a program that defines `__start` (or was it `_start`?), or a shared library...

a) building Retro68 under Haiku ... I don't see why not. Just your usual tedious let's-pick-a-fight-with-autoconf porting effort. In theory, Retro68 and all its dependencies should work out-of-the-box, in practice,...

It does look good. The disassembly you posted seems to be just the tail end of the __start function -- restores the saved value of the register r31 (`lwz`) and...