--i/VKSWANvDZSIhsB
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Fri, Feb 06, 2004 at 10:05:51AM -0500, Steven M. Bellovin wrote:
  | Following up my own post...  The problem with savage_drv.o was due to a=
=20
  | compile problem; that in turn was due to a cvs update problem at some=
=20
  | point that created a savage_driver.c with conflict notices.  How that=
=20
  | happened, I don't know, but deleting that file and redoing the CVS let=
=20
  | things build properly.
  |=20
  | But my base question remains:  what is the "right" way to build x11?

I've just added "-x" and "-X srcdir" to build.sh, which easily enable
the use of src/x11 to (cross-)build XFree86 as an integrated part of
the NetBSD build.sh process.

You can use those options, or set the relevant variables in /etc/mk.conf
(MKX11=3Dyes, X11SRCDIR=3D/path/to/src).

Cheers,
Luke.

--i/VKSWANvDZSIhsB
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (NetBSD)

iD8DBQFAJCSgpBhtmn8zJHIRAm2nAJ9N38JKbaE0goNSFUHrsb9KV09V9wCgwbMH
0KH1FtU4MW6wwyz14rb79l4=
=ckMd
-----END PGP SIGNATURE-----

--i/VKSWANvDZSIhsB--