Newsgroups: comp.os.minix
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!sol.ctr.columbia.edu!bronze!copper!templon
From: templon@copper.ucs.indiana.edu (jeffrey templon)
Subject: Re: Getting c68 to work on ST minix 1.5.10.3
Message-ID: <1991May12.144232.8081@bronze.ucs.indiana.edu>
Sender: news@bronze.ucs.indiana.edu (USENET News System)
Organization: Indiana University, Bloomington
References: <2130022@zebedee%tharr.uucp>
Date: Sun, 12 May 91 14:42:32 GMT
Lines: 41

In article <2130022@zebedee%tharr.uucp> geoffc.zebedee@tharr.uucp writes:

>the resultant file.s was empty and only contained the bss, data, text, etc
>section labels.  One article on comp.os.minix earlier suggested adding
>-DICODE to the make - I did this and when running c68 with -Qicode I just
>got an empty icode file.
>

I outlined the solution to this problem about a month ago in one of
my "hack report" articles.  It was for MacMinix but the same thing
applies for Minix ST.  You can get the article off listserv@vm1
by using "hack report" as the search field.  I would repost but it
has already expired on bronze.

The basic problem is that ACK does not report errors like it should.
ACK cannot handle the floating point code in the c68 source code;
stock ACK does not support floating point (fp).  It merrily chugs
along, though, and makes a c68 executable.  However the c68 executable
which is produced in this way is drain-bamaged beyond recognition.
This results in your "almost empty" .s files.

You have to bootstrap the compiler somehow.  CvW gave me several
suggestions on how to do this.  The most useful one, for me, was
to find an old comp.os.minix article which had a c68 BINARY uuencoded.
You can get this by searching listserv@vm1 -- use "68000 C compiler"
as search key.  Once you get this, you compile your NEW c68 source
(version III) with the OLD binary (I think it is from version II).
This will give you a working c68 version III.  When I got to this
stage, I re-compiled vIII with the vII-produced vIII executable,
just in case.

>Finally, I have all the lib68k and liback .s files - what do I do with them ?
>I presume that they go to make up some sort of new library (is this libc68.a?)
>or am I even more off track.
>

There is probably a more "correct" thing to do, but what *I* did was just
shove them into libc.a using the ar command.  I did assemble them into
.o files first.

					JT
