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

On Sun, May 01, 2005 at 06:11:24PM -0500, Richard Rauch wrote:
  | On Mon, May 02, 2005 at 09:01:10AM +1000, Luke Mewburn wrote:
  | > On Sat, Apr 30, 2005 at 12:28:39AM -0500, Richard Rauch wrote:
  | >   | I was trying to cross-build a 1.6 release from a 2.0 system.
  | >   | The build failed, but it seems that build.sh installed the
  | >   | old, 1.6 crt*.o libraries on my 2.x system.
  | >=20
  | > How did you invoke build.sh, and what build-related environment
  |=20
  | ./build.sh -M/raid/0/kernobj-1.6 -T/raid/0/tools-1.6 kernel=3Dodysseus
  |=20
  | ...I believe.  Or some such.  This is pretty much what I normally do
  | for building -current, save that I wanted a 1.6-variation on the path
  | names to separate from -current.

(see below).


  | > (Also, are you aware that the syntax for build.sh changed from 1.6 to
  | > 2.0?)
  |=20
  | No.  What kinds of changes took place?

The build.sh syntax changed.  The keyword based syntax was introduced
for 2.0 ("distribution", "sets", "kernel=3D....", (etc.)).
Compare the latest version from
    http://cvsweb.netbsd.org/bsdweb.cgi/src/build.sh?only_with_tag=3Dnetbsd=
-1-6
with that from
    http://cvsweb.netbsd.org/bsdweb.cgi/src/build.sh?only_with_tag=3Dnetbsd=
-2

That said, the build.sh in 1.6 shouldn't be building to DESTDIR=3D/
without effort, and I can't easily see why it did so for your invocation,
nor why /usr/include (et al) on your host (build) system was modified.

--wj9ZLJVQDRFjGSdK
Content-Type: application/pgp-signature
Content-Disposition: inline

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

iD8DBQFCdYaJpBhtmn8zJHIRArXlAKCEx0TTD9Bv+24m0qkRGX1B9pxlzQCggkdd
Ihfo15uWUv/GfaWB5GIfsrw=
=6gFL
-----END PGP SIGNATURE-----

--wj9ZLJVQDRFjGSdK--