Path: utzoo!censor!geac!torsqnt!news-server.csri.toronto.edu!rutgers!cs.utexas.edu!uunet!pdn!tscs!tct!chip
From: chip@tct.uucp (Chip Salzenberg)
Newsgroups: comp.unix.sysv386
Subject: Re: GNU G++ and libg++ ON ESIX REV D
Keywords: Trouble compiling libg++
Message-ID: <278222B1.A7F@tct.uucp>
Date: 2 Jan 91 18:13:04 GMT
References: <126@bsts00.UUCP> <1990Dec27.071639.3343@usenet.ins.cwru.edu> <52092@bigtex.cactus.org>
Organization: Teltronics/TCT, Sarasota, FL
Lines: 17

According to james@bigtex.cactus.org (James Van Artsdalen):
>In <1990Dec27.071639.3343@usenet.ins.cwru.edu>, ernie@po.CWRU.Edu wrote:
>> the fsf ... lack of interest in sysv/coff type things.
>
>It may not be strictly lack of interest.  It may also be lack of
>apparent need.

Exactly.  When I first ported gcc 1.37.1 to SCO UNIX, I used a
gas+COFF configuration.  I submitted my changes to Richard Stallman.
He requested that I change my patches to use the standard assembler if
possible.  I did so.  As a result, my patches were much smaller, yet
had equivalent functionality; and they didn't require gas.  That's why
gcc 1.38 supports SCO UNIX out of the box.  Er, tape.  Er, wire.  :-)
-- 
Chip Salzenberg at Teltronics/TCT     <chip@tct.uucp>, <uunet!pdn!tct!chip>
"Please don't send me any more of yer scandalous email, Mr. Salzenberg..."
		-- Bruce Becker