Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!uunet!mcsun!sunic!tut!utu.fi!mea
From: mea@utu.fi (Matti Aarnio)
Newsgroups: gnu.gcc.bug
Subject: Re: porting GCC to SCO UNIX V/386 (3.2)
Message-ID: <1990Jan9.083817.15814@utu.fi>
Date: 9 Jan 90 08:38:17 GMT
References: <8912312116.AA12256@ucscc.UCSC.EDU> <265@txsil.lonestar.org>
Reply-To: mea@polaris.UUCP (Matti Aarnio)
Distribution: gnu
Organization: University of Turku, Finland
Lines: 32

In article <265@txsil.lonestar.org> steve@txsil.lonestar.org (Steve McConnel) writes:
>In article <8912312116.AA12256@ucscc.UCSC.EDU> sef@kithrup.com (Sean Eric Fagan) writes:
>>>Has anyone successfully ported gcc to SCO UNIX V/386?  i've spent this week
>>>working on it, learning more about COFF (and a.out) format than i ever
>>>wanted to know, but still nothing works.  
...
>Thanks for the response (thanks also to those who replied via email).
>I did have to fiddle with the definition of FFS, now that you mention it.
>It turns out that i was using the tm-i386v.h configuration, and trying to
>use gas.  Silly me.  At the moment, I'm using COFF all the way, with the
>AT&T assembler and linker.  This seems to work okay.  Of course, as i
>understand the installation instructions, this also precludes gdb :-(.  If
>i have time, i'll see if the COFF encapsulation works any better with
>tm-i386gas.h, but at least now i have a working gcc, and can take a look at
>g++ now.

  I am using Gcc 1.36 with AT&T assembler, without any problems.
I also get nice gdb informations out of it.
Umm..  I did  'make i386v' (or something like it), without modifying
any sources on this  ISC 2.0.2 ix/386 that I have.
Later on I have applied one patch from RMS to avoid fault on statement:

   float ff = 1e100;

:-)  (It was in 3dplot program for X-windows, not in my own code)

>-- 
>Stephen McConnel
>Dallas, TX 75236              Internet: steve@txsil.lonestar.org

	/Matti Aarnio	<mea@mea.utu.fi>
	 Finnish Academic and Research Network Project (FUNET)