SQ79%liverpool.ac.uk@nsfnet-relay.ac.uk (Mark Powell) (09/15/89)
My suggestion to of how to change the ACK compiler is: MAKE IT WORK Ahhh, Memory Fault. Probably the most frequent diagnostic to come out of ST Minix. Well it's not that bad, but the number of times I've had memory fault spew out of something is getting a bit beyond the pail (pale?) Source code that has compiled (and works) successfully on the PC just memory faults on the ST. Other than nroff various source has done this. A compiler bug... never. For example: I transfered PC1.4a init.c to my ST and added to my minix.img. What happened? You guessed it our old friend Memory fault. I looked at the source, seems okay! Tweaked a few bits that should have worked, but weren't exactly K&R. Still memory faulted. It was the updating the wtmp file that memory faulted, so I deleted the code and imported the wtmp updation routine from login.c, which I might add works perfectly! RE-compiled it memory fault. ARRGHHHH! Deleted the routine again and re-wrote it so that it did exactly the same thing (updated the wtmp file), but in a different way. Re-compiled it... worked okay! ST & PC Minix compilers.. compatible? Naahh! Well they successfully compile each others source, but what they compile it into is a different story. Could we have old chestnuts like the compiler sorted out, before all this POSIX stuff is done. Surely, a working compiler takes higher priority than standards, afterall what are you going to compile this standard code on? Mark Powell ARPA sq79%liv.ac.uk@nsfnet-relay.ac.uk UUCP ...!mcvax!ukc!liv.ac.uk!sq79