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

On Sat, Jul 09, 2005 at 12:03:46PM -0400, Chuck Swiger wrote:
  | Jens Gran wrote:
  | >On 7/9/05, Stefan Schumacher <stefan@net-tex.de> wrote:
  | [ ... ]
  | >I mean only kernel's source and tools which need to build it on anothe=
r OS.
  | >And of couse I already have pmake, gcc, sh and so on things.
  | >
  | >So
  | > gnusrc.tgz . . . . . . . . . . . Mar 30 17:03     76M=20
  | > sharesrc.tgz . . . . . . . . . . Mar 30 17:03   4783K=20
  | > src.tgz. . . . . . . . . . . . . Mar 30 17:03     36M=20
  | > syssrc.tgz . . . . . . . . . . . Mar 30 17:03     26M=20
  | > xsrc.tgz . . . . . . . . . . . . Mar 30 17:03     81M=20
  | >
  | >I need all this stuff to build kernel?
  |=20
  | In theory, all you would need is syssrc, not the rest.
  |=20
  | In practice, the kernel and libc need to agree on the system call=20
  | interface, so you either need to build the kernel against an existing=
=20
  | NetBSD userland (or "world"), or you need to build world to have that=
=20
  | available to build a usable kernel.
  |=20
  | Be warned: trying to cross-compile a kernel on some other platform is a=
=20
  | wizard-level operation involving serious black magic.

No it isn't:
	./build.sh tools kernel=3D/path/to/kernelconfig
I've been using that since before NetBSD 2.0 was released.

Of course, to use that you'll probably need all source sets extracted. =20

--Ca0e2zgpnh8/XhnM
Content-Type: application/pgp-signature
Content-Disposition: inline

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

iD8DBQFC0cSBpBhtmn8zJHIRApH7AJ97AX4sm1yQvuFqijTQfzKyLjnpZACgjQAi
Rwzfy8sZWVl/FOWHP/7KPH8=
=uf0J
-----END PGP SIGNATURE-----

--Ca0e2zgpnh8/XhnM--