--Z/kiM2A+9acXa48/
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Fri, Apr 12, 2002 at 08:35:21AM -0400, Todd Vierling wrote:
> ./build.sh -t [-T $TOOLDIR]
> cd sys/arch/$MACHINE/conf
> $TOOLDIR/bin/nbconfig $KERNCONFNAME
> cd ../$KERNCONFNAME
> $TOOLDIR/bin/nbmake-$MACHINE all
>=20
> This corresponds to established practice for building a custom kernel; it
> just uses the cross-toolchain created by "build.sh -t".

I don't think that'll work on a non-current system (or even out of
date -current). The build process calls tools other than ${MAKE},
and if they're not set ahead of time, you won't get the nb* version.

I don't remember what bit me, but I know I've been bit by it before
(which is why I just let build.sh build my kernels by including
EXTRA_KERNELS in /etc/mk.conf and always giving build.sh the -R
flag).

Unless, of course, you've noticed this and fixed it since last I
tried. :^>

--=20
gabriel rosenkoetter
gr@eclipsed.net

--Z/kiM2A+9acXa48/
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (NetBSD)
Comment: For info see http://www.gnupg.org

iEYEARECAAYFAjy3GQIACgkQ9ehacAz5CRqH3wCgmsSvZcJkXN7W3HIGwSW5kMOs
i2sAmgPEIz10YddNgkramA+wGfFSXUty
=1d9O
-----END PGP SIGNATURE-----

--Z/kiM2A+9acXa48/--