In article <Pine.NEB.4.51.0412101544150.28553@lothlorien.starwolf.com>,
	greywolf@starwolf.com (Greywolf) writes:
> 
> JC: If you wanted those to be /library, more power to you, but there's
> JC: only so many knobs provided in the build system. (and none of them
> JC: re-organize where stuff gets installed, only whether or not a given
> JC: feature is enabled).
> 
> Oh, come ON.  I have ALWAYS been able to tell X11 where the hell to install.
> This has NOTHING TO DO with whether I am going to make /library, /binary
> or other such nonsense.  X11's install base has ALWAYS been configurable.
> 
> The thing that I find really annoying is that when I built X to be installed,
> it ALSO seemed to want to ignore ProjectRoot in my site.def file, for
> some reason.

What are you saying? That the NetBSD reachover build ignores "site.def"?
Of course it does -- "site.def" is for "imake". If you want to set stuff
in "host.def" or "site.def" and do a "make World" in ".../xc", that *did*
work the last time I tried it.  Some of the new X servers have not been
integrated with the out-of-the-box build, as far as I can tell, but they
should just be ignored.  If we've broken the "make World" build, I'd say
that's a bug, but I suspect not.

XFree86 has been doing native builds, and distributing binaries for,
NetBSD 1.6.2. If you check out from them and "make World" doesn't work,
you can file a bug report with them. I was installing lead-ups to XFree
4.4.0 against lead-ups to NetBSD 2.0 into a different ProjectRoot, and
never ran into a build problem.  The one significant difference between
our build and their build, is that their "xdm" doesn't support "xdmauth"
without patching as directed (which NetBSD has done).

This "reachover build" had been on the wish list for a long time.
Why...?

1) You can now build a single program or library from "xsrc" without
having to do a full "make World" as a prerequisite.

2) You can now build a NetBSD release without messing up your "xsrc".

3) The "original" XFree86 is still in the tree, virtually untouched,
for whatever purpose you might put to it.

4) You can now cross-build xsets using the "build.sh" toolchain, as
easily as adding "-m arch" to build.sh's arguments.

lukem and rtr committed all this in September 2003, by the way, with
no objections, so it's not like this is a live issue.


Frederick