[Coco] 3rdPart Editor
ooogalapasooo at aol.com
Mon Dec 17 00:37:33 EST 2018
Bill, a lot of the problem you're having is a 30 year old "make" utility, trying to make a modern "makefile".
The make in the NitrOS9 C compiler package will in no way make the makefiles used in the repo. Make has come a long way since 1985.
I'm not sure which make is in the repo as there are 2. One is the Microware version that came with the original C compiler. The other is Tim Koonce's make which supports a little more and isn't tied to specific drives like the old one. Syntax between the two are similar, but there are differences. What little bit of a manual there is for TK's make (help files) is on RTSI. Microware's make docs are in the C Compiler manual.
From: Gene Heskett <gheskett at shentel.net>
To: coco <coco at maltedmedia.com>
Sent: Sun, Dec 16, 2018 2:23 pm
Subject: Re: [Coco] 3rdPart Editor
On Sunday 16 December 2018 13:52:56 Bill Gunshannon wrote:
> On 12/16/18 1:19 PM, Gene Heskett wrote:
> > On Sunday 16 December 2018 11:42:50 Bill Gunshannon wrote:
> >> Just out of curiosity, has anyone ever built the version of the
> >> Unix editor "ed" that is in the 3rdparty/packages directory?
> >> Additionally, is there any documentation on the "make"
> >> command packaged with the C Compiler? It does not seem to
> >> take any syntax used by other versions of make.
> >> bill
> > That to me is an odd comment Bill, its the first make I ever used,
> > and it always did what I asked. But it doesn't have all the bells
> > and whistles the current *nix make has.
> Odd comment? Why? I tried it with the "ed" editor. Does
> a lot of weird stuff including inserting flags for the C Compiler
> that are not anywhere in the makefile itself. Doesn't seem to
> recognize the section labels at all. (Like all: clean:, etc. )
> make all
> make: Can't find source file to make "all.r"
> It's fun to play with it again (I have my system running with two
> decent sized IDE disks!) but I am finding very little that works as
> Got "ed" built, but not using either the scripts or the makefile
> provided. Working on SmallC.
Part of that may be smallC, it would/could be a lot different from either
of the K&R reference books. The coco's C is pretty much the original K&R
minus much of the bit twiddling, meaning you have to write your own. Not
a big deal. The 6x09's not having a "barrel shifter" makes the hand
tweaks much more attractive as the default is a one bit at a time loop,
eg long shifts take a long time. There are ways to throw away the time
for 8 bit and up shifts. Paul Jerkatis was run off this list 20 years
ago because his idiot of a CS prof said it couldn't be done. I sent a
short 6 or 7 line code snippet as proof. He was determined there was a
side effect, but the only side effect was doing an 8 bit shift in less
time than the compilers default method for a 1 bit shift.
That diff would be enough to chase me off of smallC regardless of the
hardware you're useing, which I gather is not a real coco. What I'm
writing here _always_ assumes its a real coco. I've never had the urge
to try any of the emulators. My fault probably Bill, but there it is. :)
> Got it to compile (again, not
> using the makefile, I compiled it by hand.) but while it worked
> fine on other systems it can't even read hello.c. And all it
> really does is read a source file and write out an assembler file.
> But I will plug on. Maybe I can find some utilities that can make
> the job easier.
Cheers & Merry Christnas to you and yours, Gene Heskett
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page <http://geneslinuxbox.net:6309/gene>
Coco mailing list
Coco at maltedmedia.com
More information about the Coco