Xref: utzoo unix-pc.general:815 comp.sys.att:3477
Path: utzoo!attcan!uunet!lll-winken!lll-lcc!ames!umd5!umbc3!alex
From: alex@umbc3.UMD.EDU (Alex S. Crain)
Newsgroups: unix-pc.general,comp.sys.att
Subject: Re: GNU C, GNU g++ & 2400 baud microcom
Message-ID: <1015@umbc3.UMD.EDU>
Date: 13 Jun 88 17:23:01 GMT
References: <1118@unisec.usi.com>
Reply-To: alex@umbc3.UMD.EDU (Alex S. Crain)
Organization: University of Maryland, Baltimore County
Lines: 25

In article <1118@unisec.usi.com> dpw@unisec.usi.com (Darryl P. Wagoner) writes:
>Greetings,
>
>I have two questions, first what changes are need to get the gnu cc to
>working on the Unix PC? (ex: ld, shared library & config files).  I know
>this is a repeat issue but I didn't have a interest until I got g++.  BTW
>I have version 1.22 of GCC.

	I ported gcc-1.18 to work on the unixpc, and was working on 1.22
until I found the last bug in the assembler and got so disgusted that I gave
up. It is my opinion that the unixpc assembler is too stupid to cope with
gcc past v1.18, although I think that some others are working on keeping things
up to date.

	I will spend the summer (or less) porting gnu ld & as so that there 
will be a decent assembler for this box. In the meantime, I still have diffs
for gcc-1.18, and well send them out to anyone interested. 

BTW: I use gcc-1.18 as my default compiler because I find it superior to 
/bin/cc even without debugging support. (I will recompile w/ cc if I really
need sdb)

-- 
					:alex.

nerwin!alex@umbc3.umd.edu
alex@umbc3.umd.edu