[Oberon] Fwd: Ulm Oberon

[Jan de Kruyf]

Small mistake, this should go to the list.


Joerg

Here is how to contruct ELF files. Not for you so much, but whoever comes
after us:

http://sourceforge.net/projects/elftoolchain/files/Documentation/libelf-by-example/20120308/

download the pdf.

the issue it appears is not bitrot. It is a student :) and a very
convenient unix box for bootstrapping, that we now dont have.
Das ist eine von die Unschönheiten, wie der Borchert damals sagte.
The oberon object files are more or less rightly disassembled, but the
fault is in the building of the ascii tables: there is exactly one name in
the elf file.
In any case: it is the usual building of C fairy castles with lots of
pointers pointing and offsets offsetting and drummers drumming and so on.
And then at the end libelf graciously writes the fairy castles to disk for
us. So plenty of room for mistakes and no good way of debugging afterwards,
unless you break into the kernel source files.

So I think I will perhaps rebuild the fairy castles 'working bit' by
'working bit' and write to disk and test after each added bit, to see what
is produced. It is maddening.

cheers,

j.


On Thu, Oct 15, 2015 at 9:35 AM, Jörg <joerg.straube at iaeth.ch> wrote:

> Jan
>
> 1)    Ulm: No. I don’t have time to try.
>
> 2)    Pattern matching: If you are interested I can send you my matching
> procedure J
>
> br
>
> Jörg
>
>
>
> *From:* Oberon [mailto:oberon-bounces at lists.inf.ethz.ch] *On Behalf Of *Jan
> de Kruyf
> *Sent:* Mittwoch, 14. Oktober 2015 11:10
> *To:* ETH Oberon and related systems
> *Subject:* Re: [Oberon] Ulm Oberon
>
>
>
> Got it. Thanks.
>
>
>
> I like it for the excellent doku and it comes nearest to a linux
> programming environment
>
> and also I did find the Borchert dissertation about the library design.
>
> But he was not scared of adding layers of German complexity.
>
>
>
> Did you get that system to go Joerg?
>
>
>
> jan.
>
>
>
>
>
> On Wed, Oct 14, 2015 at 8:34 AM, Jörg Straube <joerg.straube at iaeth.ch>
> wrote:
>
> Look at „I386OberonTransportableObjectFormat.om“
>
>
>
> Jörg
>
>
>
> Am 13.10.2015 um 21:59 schrieb Jan de Kruyf <jan.de.kruyf at gmail.com>:
>
>
>
> Hallo,
>
>
>
> Has anybody got any idea where to find the spec for the 'tof' intermediate
> file that the compiler produces?
>
>
>
> The tof2elf program has bitrotted, the 'elf' it produces is corrupt
> according to 'ar' , 'nm' and 'ld'.
>
> None of the present day elf formats (as in nm) work on it. And readelf
> complains about corrupt Section Header names.
>
>
>
> There is not much to the program but it would be handy to have the file
> spec.
>
>
>
> It would be nice to resurrect that old beast.
>
>
>
> cheers,
>
>
>
> j.
>
>
>
> --
> Oberon at lists.inf.ethz.ch mailing list for ETH Oberon and related systems
> https://lists.inf.ethz.ch/mailman/listinfo/oberon
>
>
>
>
> --
> Oberon at lists.inf.ethz.ch mailing list for ETH Oberon and related systems
> https://lists.inf.ethz.ch/mailman/listinfo/oberon
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.inf.ethz.ch/pipermail/oberon/attachments/20151015/166333fa/attachment.html>