Path: utzoo!censor!geac!torsqnt!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!caen!ox.com!emv
From: srodawa@vela.acs.oakland.edu (Ron Srodawa)
Newsgroups: comp.archives
Subject: [sco-xenix] Re: GNU & SCO 2.3.1
Message-ID: <1990Dec4.180245.29198@ox.com>
Date: 4 Dec 90 18:02:45 GMT
References: <1990Nov28.220003.4139@hoss.unl.edu> <36395@cup.portal.com> <4073@vela.acs.oakland.edu>
Sender: emv@ox.com (Edward Vielmetti)
Reply-To: srodawa@vela.acs.oakland.edu (Ron Srodawa)
Followup-To: comp.unix.xenix.sco
Organization: Oakland University, Rochester MI
Lines: 45
Approved: emv@ox.com (Edward Vielmetti)
X-Original-Newsgroups: comp.unix.xenix.sco

Archive-name: gnu/gcc/xenix/1990-12-01
Archive-directory: unix.secs.oakland.edu:/pub/xenix/gcc/ [141.210.180.2]
Original-posting-by: srodawa@vela.acs.oakland.edu (Ron Srodawa)
Original-subject: Re: GNU & SCO 2.3.1
Reposted-by: emv@ox.com (Edward Vielmetti)

In article <36395@cup.portal.com> Perry_Lee_Statham@cup.portal.com writes:
>Has anyone successfuly compiled the GNU software (specifically gcc and gdb)
>under SCO Xenix 2.3.1?  How do I set up my #define's? Do I need to modify my
>include files that came with the development system? What version of System V
>is Xenix really (I only see options for ver III)?
>
>ANY HELP WOULD BE APPRECIATED!!!

It is more important what level of the development system you have.  I have
successfully built everything, including g++ and glib++.  I'll be
packaging it somehow (easiest way for me) and making it available via
anonymous ftp for those on the internet.

1. To build gcc and friends, you want to get the three diskette set that
recently originated at RoboBar thanks to Steve and Ron.  This consists of
three files (not diskettes) which build two diskettes suitable for custom.
The third file is instructions.  There is a copy on unix.oakland.edu
(141.210.180.2) for anonymous ftp in the directory /pub/xenix/gcc.  You
get best results if compiling with the gcc binary included.  The easiest
way to start is to use -traditional option to gcc.  In that case you
probably don't have to modify your include files.

2. To build g++, you need to install the source for gcc updated for
Xenix (patches and instructions included on those gcc diskettes).  I had
a bit of trouble with the include files, but finally got it all to go.

3. After installing g++, then you can make libg++.  Again, minor problems
with include files will haunt you.

4. I forgot to say..as a part of (2), you need the set of g++ patches which
Ron and Steve posted to the net.  This includes a script to modify the
include files.  I'll be posting this, along with the binaries, next week.
Ron.

-- 
| Ronald J. Srodawa               | Internet: srodawa@unix.secs.oakland.edu |
| School of Engineering and CS    | UUCP:     srodawa@egrunix.UUCP          |
| Oakland University              | Voice:    (313) 370-2247                |
| Rochester, Michigan  48309-4401 |                                         |


Brought to you by Super Global Mega Corp .com