Xref: utzoo comp.unix.i386:6709 comp.unix.xenix:12390
Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!cs.utexas.edu!usc!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!aplcen!wb3ffv!ka3ovk!raysnec!shwake
From: shwake@raysnec.UUCP (Ray Shwake)
Newsgroups: comp.unix.i386,comp.unix.xenix
Subject: Re: Xenix vs. UNIX
Summary: GCC - for the few... the proud... the persevering
Message-ID: <99@raysnec.UUCP>
Date: 9 Jul 90 21:00:58 GMT
References: <3304@crash.cts.com> <4716@thebes.Thalatta.COM> <1990Jun27.232700.3046@virtech.uucp> <1990Jun29..185@rdk386.uucp>
Reply-To: shwake@raysnec.UUCP (Ray Shwake)
Followup-To: comp.unix.i386
Distribution: usa
Organization: IRS - ACI Project Office
Lines: 20

In article <1990Jun29..185@rdk386.uucp> ron@rdk386.UUCP (Ron Kuris) writes:
>
>Why not just use gcc and not worry about the abnormalities of the "standard"
>compiler provided with Xenix?  I agree its broken, but the compiler doesn't
>make the entire system unusable, especially when there are alternatives...

	This response is just a tad facile for my taste. GCC doesn't always
	make life easier. I had my first encounter with GCC last week after
	a colleague installed it on his Sequent Balance. Well, here was an
	opportunity to see what all the fuss was about. Moved some of my
	source over, checked flags and file locations, typed "make".

	Given my System V biases, tried compiling in the ATT environment.
	Had to modify a few macro contructs to make them "ansi conformant",
	but things got REAL interesting in the link/load phase. It just
	couldn't find the c runtime module! Found the module in /.lib
	(that damn universe again!). OK, back to BSD. Argh! Can't find
	_regex, _strchr, ...

	Morale: GNU CC... It *might* work for you.