Path: utzoo!attcan!uunet!lll-winken!ames!sun-barr!apple!bloom-beacon!EXPO.LCS.MIT.EDU!jim
From: jim@EXPO.LCS.MIT.EDU
Newsgroups: comp.windows.x
Subject: Re: X Installation woes
Message-ID: <8905111839.AA24837@expo.lcs.mit.edu>
Date: 11 May 89 18:39:28 GMT
References: <30501@sri-unix.SRI.COM>
Sender: daemon@bloom-beacon.MIT.EDU
Organization: X Consortium, MIT Laboratory for Computer Science
Lines: 41


> X installation instructions leave a great deal to be desired.

Then please submit suggestions to xbugs@expo.lcs.mit.edu on how they can
be improved next time.


> A month ago back when we were running Sys4-3.2, I gave up trying
> to install X11R3 on my Sun4. It was far easier just moving up 4.0.3

Not surprising in the least.  The release notes explicitly say:


				4.3+tahoe
		Ultrix 3.0 FT2 (also compiles under Ultrix 2.0)
				SunOS 3.4
				HP-UX 6.01
	    Apollo Domain/IX 9.7 (and 9.6 according to its developers)
		IBM AOS 4.3 (according to its developers)
				 A/UX 1.0

	If you are using versions prior to these, you may run into trouble.


We didn't have a Sun3 running SunOS 4.0 on which to test, we weren't able to
isolate all of the SPARC compiler bugs from the 4.0 compiler bugs.  Sorry.  We
try to make our software install and run on a wide range of platforms, but
coping with every old version of every operating system isn't something we're
set up to do. 


> Now that I have the core X running (and it works fine), just how
> do I install non-core X, that vast mass of software in contrib that
> "make World" refuses to touch?

The same way you'd do it if you got it from a friend, or off the net, or ....
The contributed software portions of the MIT releases are a grab bag.  The core
build procedure doesn't touch them, by default, because we haven't verified
that they build on all of our platforms.  But, since we'll be requiring
Imakefiles for all contributed software in R4, this will hopefully be less of a
problem.  But, you'll probably still have some work to do.