Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uwm.edu!spool2.mu.edu!uunet!mcsun!unido!pbinfo!marc
From: marc@uni-paderborn.de (Marc Gumbold)
Newsgroups: comp.os.minix
Subject: Re: Again: compiling c68 with ACK
Message-ID: <1991Jan15.205856.18619@uni-paderborn.de>
Date: 15 Jan 91 20:58:56 GMT
References: <41579@nigel.ee.udel.edu>
Organization: Uni-GH Paderborn
Lines: 40

HBO043%DJUKFA11.BITNET@cunyvm.cuny.edu (Christoph van Wuellen) writes:

>[...]

>A cc.c that supports c68 was posted with c68, Version II, patchlevel 5.
>It is trivial, you can do it by hand.
>The commands to generate for compiling, say, source.c, are:

>/usr/lib/cpp source.c > /tmp/TEMP_FILE_NAME.i
>/usr/lib/c68 /tmp/TEMP_FILE_NAME.i /tmp/TEMP_FILE_NAME.s
>rm /tmp/TEMP_FILE_NAME.i
>/usr/bin/as - /tmp/TEMP_FILE_NAME.s -o source.o

I did just that with my ACK-compiled c68. But whenever I feed cpp
output to c68 it will produce almost empty (besides text ..., data ...)
.s-Files.

Is that the kind of misbehaviour of ACK-compiled c68 you referred to
in your earlier posting?

If I compile a "hello world" free of cpp commands with c68, it works
fine; I get a correct .s-File which I can get to run (with "old"
linker and cv).

BTW: Where can I find the new ld/cv you mentioned?

>You need not change code in cc.c, just change some table entries.

Having no source of cc (as is the default with normal Minices) that
is going to be difficult... :-)

So: Suitable cc and/or new ld/cv ftp'able from somewhere?

>C.v.W.

-- 

 Marc Gumbold         EMail: marc@uni-paderborn.de   Phone(home): +49 5234 5319 
 grad CS stud         Snail(home): Nordstr. 29, 4934 Horn-Bad Meinberg, Germany
 ------ "Forty-two," said Deep Thought, with infinite majesty and calm. -------