john@bradley.bradley.edu (John Lengeling) (01/11/91)
I have an Altos 1000 running System V 5.3.1e and I would like to get a C compiler for it. Would GCC work? If so, is there someone who can send me the binaries or am I out of luck and have to buy a C compiler? John Lengeling john@bradley.edu -- --- "How many O's is that?" John Lengeling
allbery@NCoast.ORG (Brandon S. Allbery KB8JRR) (01/12/91)
As quoted from <1991Jan10.172451.23966@bradley.bradley.edu> by john@bradley.bradley.edu (John Lengeling): +--------------- | I have an Altos 1000 running System V 5.3.1e and I would like to | get a C compiler for it. Would GCC work? If so, is there someone | who can send me the binaries or am I out of luck and have to buy a C | compiler? +--------------- You're out of luck --- but not because you can't get gcc binaries. C ompilers do not exist in a vacuum. You need the compiler, assembler, linker, and the C standard library. If you're willing to put up with the nonsensical "COFF encapsulation" that RMS & Co. use to make System V binaries look like BSD binaries, the first three can be solved; but the C standard library, libc.a, is not available yet from the FSF --- and if it were, you'd need a way to compile (or, in the case of most system calls, assemble) the low-level routines in a way compatible with the Altos 1000. The only real option is to buy the regular development system from Altos. Once that's done, however, gcc is a better compiler than the pcc port provided by Altos, and MUCH MUCH better than the Microsoft C compiler. gcc builds unchanged using the configuration for 386/ix. ++Brandon -- Me: Brandon S. Allbery VHF/UHF: KB8JRR on 220, 2m, 440 Internet: allbery@NCoast.ORG Packet: KB8JRR @ WA8BXN America OnLine: KB8JRR AMPR: KB8JRR.AmPR.ORG [44.70.4.88] uunet!usenet.ins.cwru.edu!ncoast!allbery Delphi: ALLBERY
ti@altos86.Altos.COM (Ti Kan) (01/30/91)
In article <1991Jan10.172451.23966@bradley.bradley.edu> john@bradley.bradley.edu (John Lengeling) writes: >I have an Altos 1000 running System V 5.3.1e and I would like to >get a C compiler for it. Would GCC work? If so, is there someone >who can send me the binaries or am I out of luck and have to buy a C >compiler? Altos offers the Altos System V Development System package for the System 1000, which includes the C compiler, libraries, header files, and many other development tools including SCCS. Please contact your Altos dealer for information. I don't know if anyone has tried gcc on the System 1000, if anyone has I would like to know. -Ti -- Ti Kan | vorsprung durch technik! \\\ Internet: ti@altos.com \\\ UUCP: ...!{sun|sco|pyramid|amdahl|uunet}!altos!ti /// \\\ The opinions herein are not necessarily those of Altos. ////////\
allbery@NCoast.ORG (Brandon S. Allbery KB8JRR) (02/01/91)
As quoted from <4650@altos86.Altos.COM> by ti@altos86.Altos.COM (Ti Kan): +--------------- | In article <1991Jan10.172451.23966@bradley.bradley.edu> john@bradley.bradley.edu (John Lengeling) writes: | >I have an Altos 1000 running System V 5.3.1e and I would like to | >get a C compiler for it. Would GCC work? If so, is there someone | >who can send me the binaries or am I out of luck and have to buy a C | >compiler? | | Altos offers the Altos System V Development System package +--------------- This would have been more appropriate via mail.... +--------------- | I don't know if anyone has tried gcc on the System 1000, if anyone | has I would like to know. +--------------- I have. Gcc works fine on the Altos 500/600/1000/2000 when compiled with the settings for 386/ix. However, gdb doesn't seem to like them too much; I gave up on making it work. In any case, I include a summary of what I said in *my* mail to John: Having a C compiler isn't enough. To build a program, you need not only a compiler, assembler, and linker (all available from the FSF if you don't mind the GNU General Public Virus) but also a library of system calls and C standard library functions (like stdio) and the header files to match. The FSF hasn't come up with a full C library yet, and they *certainly* wouldn't have system call libraries that would work on a System V/386 system. Worse, the GNU ld won't work with System V libraries, due to a bad case of NIH on the part of whoever wrote it: rather than learn how to use COFF, they put a minimal COFF wrapper around a BSD executable. This wrapper is created only around executables; object files (including those in archives) are in BSD format and therefore incompatible with any other library on the system. (Oh, sure, there's a converter to turn COFF objects into BSD objects, but it dies on anything with .init and .dnit segments. These segments are used to provide the functionality that the FSF claims is missing from COFF and thereby requires GNU ld to be used with g++. Go figure.) ++Brandon -- Me: Brandon S. Allbery VHF/UHF: KB8JRR on 220, 2m, 440 Internet: allbery@NCoast.ORG Packet: KB8JRR @ WA8BXN America OnLine: KB8JRR AMPR: KB8JRR.AmPR.ORG [44.70.4.88] uunet!usenet.ins.cwru.edu!ncoast!allbery Delphi: ALLBERY