Path: utzoo!utgpu!watserv1!watmath!att!ucbvax!PAN.SSEC.HONEYWELL.COM!thompson From: thompson@PAN.SSEC.HONEYWELL.COM (John Thompson) Newsgroups: comp.sys.apollo Subject: re: crt0.o -- C compiler revision Message-ID: <9008301333.AA13308@pan.ssec.honeywell.com> Date: 30 Aug 90 13:33:49 GMT Sender: daemon@ucbvax.BERKELEY.EDU Organization: The Internet Lines: 47 > While checking out a problem for someone, I discovered that > /usr/lib/crt0.o (and gcrt0.o and mcrt0.o) had the following makers - > > bind mcrt0.o -mak > > This object was made by the following: > ASM, Rev 9.10, Date: 1988/05/09 18:06:14 BST (Mon) > C compiler 68K Rev 6.7(232) - BETA TEST, Rev 0.00, Date: 1989/06/21 > 15:02:00 BST (Wed) > ld, Rev 10.01, Date: 1989/05/10 20:27:26 BST (Wed) > > > Should it concern us that a BETA TEST C compiler was used, and (more > importantly) has this compiler been used for other system executables? I wouldn't be bothered too much by it. In theory, beta software has been tested out well enough that you want an outside source to abuse it. This seems to imply (IMHO) that the developers are comfortable with it. Additionally, you run into a chicken-and-egg problem eventually. Something needed to be made with a beta release at some point in the past. Should we trust it? What about anything that's been made after that? To answer your second question, I'd assume that other stuff was made with beta software. What _I_ found was stuff made with ALPHA compilers! Specifically, the /lib/clib (ts 1989/10/05 14:46:55 CDT) was built with $ bind //gollum/lib/clib -mak This object was made by the following: bind, Rev 6.10, Date: 1989/03/06 18:36:30 CDT (Mon) ASM, Rev 9.10, Date: 1989/07/21 10:17:09 CDT (Fri) Pascal compiler PRISM=>68K Rev 8.7(226) - ALPHA TEST, Rev 0.00, Date: 2015/09/05 0:58:26 CDT (Sat) Pascal compiler 68K Rev 8.7(127) - ALPHA TEST, Rev 0.00, Date: 1989/05/09 13:06:29 CDT (Tue) C compiler PRISM=>68K Rev 6.7(301), Rev 0.00, Date: 2015/09/05 0:58:26 CDT (Sat) C compiler 68K Rev 6.7(299), Rev 0.00, Date: 1989/08/08 13:11:00 CDT (Tue) John Thompson (jt) Honeywell, SSEC Plymouth, MN 55441 thompson@pan.ssec.honeywell.com As ever, my opinions do not necessarily agree with Honeywell's or reality's. (Honeywell's do not necessarily agree with mine or reality's, either)