[Oberon] Compiling Original Oberon in (Unix)Aos?

[jwr at robrts.net]

Bernhard:
   Thank you!!  That very much helps me understand.

   It appears you sent this answer directly to me, and not to the  
list. Your information appears more widely useful, so I just wish to  
verify that it was your intention NOT to send it to the list.  If so,  
no action is needed.  If not, perhaps forward to the list your  
original reply to me, with slight edits so it appears to be directly  
sent to the list.  Thank you!!

-- John Roberts

Quoting Bernhard Treutwein <Bernhard at wildwein.de>:

>>   -----Original Message-----
>> From: [jwr at robrts.net]
>> Received: Samstag, 30 Jan. 2016, 22:50
>> To: [oberon at lists.inf.ethz.ch]
>> Subject: Re: [Oberon] Compiling Original Oberon in (Unix)Aos?
>>
>> [...]
>>
>> Please help me understand, I think I misunderstand something critical.
>> It sounds to me like this (UnixAOS) distribution is partially
>> "broken",
> yes it is partially broken, especially the Oberon Subsystem, which was afaik
> originally used to bootstrap A2/UnixAos/WinAos.
>> in that it is currently in a state different than it would
>> be if everything was recompiled from source. Some objects currently
>> exist with incompatible object-code formats?! Also it sounds like
>> certain source files are written in different (incompatible?)
>> "dialects" of the Oberon language. This suggests there is a
>> significant possibility that right now the release cannot be
>> completely recompiled successfully.
> The whole system can be recompiled with the FOX compiler, but the
> Oberon subsystem has not be upgraded to use FOX. The two compiler
> available in the Oberon subsystem both do not understand name spaces.
>
> Current state is (at least to my knowledge): Work in progress, and there
> is only one or two persons partial time working on it ...
>
>>
>> Recognizing that there is a chicken-and-egg problem regarding
>> bootstrapping the compiler(s) [whose solution is well known and
>> documented], are the proper procedures documented and available for
>> cleanly recompiling everything in UnixAOS from scratch? Has anyone
>> recently verified the procedures work properly? Is that useful/Does
>> anyone care?
> yes the procedures for cleanly recompiling everything are documented  
> in Build.Tool
> and Release.Mod together with Release.Tool.
>
> I don't know if the orginal way to bootstrap the system from within  
> Native Oberon
> as described in Pieter Mullers and Patrik Realis PhD theses still  
> work. The Oberon
> subsystem has still old compilers (Regis Creliers OP2 & Patrik  
> Realis PaCo), but
> both do neither understand the full current language nor do they produce the
> current object file format.
>
>> Theoretically there should be a file within the distribution which
>> describes the exact procedure (with the proper commands listed) to
>> recompile everything cleanly and properly. Perhaps not everything
>> should be compiled with the same compiler: there may be a set of files
>> compiled by the AOS compiler,
> see above ...
>> another set by Oberon compiler #1, and
>> yet another set by Oberon compiler #2, but it should somewhere be very
>> clear exactly what to do.
>>
> afaik, this is missing
> --
>   Bernhard