Xref: utzoo comp.unix.sysv386:6374 gnu.g++.help:656 gnu.gcc.help:577
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!dkwgate!twisted.dkw.com!jr
From: jr@twisted.dkw.com (J.R. Jesson)
Newsgroups: comp.unix.sysv386,gnu.g++.help,gnu.gas.help,gnu.gcc.help
Subject: Re: gcc and g++ wanted for ISC Unix.
Message-ID: <1991Mar27.170315.14587@dkwgate.uucp>
Date: 27 Mar 91 17:03:15 GMT
References: <1991Mar25.213918.13974@aie.uucp>
Sender: news@dkwgate.uucp (NewsSoftware)
Reply-To: jr@dkwgate.dkw.com
Organization: DKW Systems Corporation
Lines: 20

In article <1991Mar25.213918.13974@aie.uucp>, hansb@aie.uucp (Hans Bayle) writes:
|> 
|> Is there any place from where I can ftp g++, glib++, gcc, and gas source code 
|> configured to generate COFF objects for Interactive 386/ix 2.2?
|> 
|> I've tried the COFF patches from David Dawes at syphus.physics.su.oz.au,
|> but Interactive's ld cant handle the object files that are generated by gas.
|> I've been looking in the code, and it seems that Interactive's aouthdr.h
|> is different from the a.out.h that came with the Esix COFF patches for gas.

I would recommend that you blow off "COFF" compatability when compiling gnu
under ISC Unix.  I have gcc, gdb and g++ running, and got them running simply
by specifying the standard 386-sysv entry when configuring. In essence, because
gcc and g++ use the stock ISC assembler, you get COFF but not encapsulated
COFF.  Although you dont get some of the extended COFF stuff (and dbx records),
it's probably not much of a loss either, since you would have to duplicate all
of the system libraries you like to use (ala robbitussin), and be bound to
ranlib (isnt ranlib kind of a pain in the ass?).

J.R.