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

On Thu, Aug 25, 2005 at 10:38:47PM +0200, Rudi Ludwig wrote:
> On Wed, 24 Aug 2005 17:41:05 -0700
> Bill Studenmund <wrstuden@netbsd.org> wrote:
>=20
> > I'm not sure how to help, but the command is correct. genassym
> > GENerates ASsembly SYMbols, and is used to generate defines that
> > indicate how far into a struct assembly-language code should find
> > parts of C structures.   That way if you shuffle C-language structures
> > around, the asm code can automatically keep up.
> >=20
> > I'm not sure where it gets built by default these days, but go
> > searching  for it.
>=20
> Okay, I see, carefully re-reading the
> http://www.netbsd.org/Documentation/kernel/#how_to_build_a_kernel
>=20
> I think I understand that I cannot build -current (3.99.xx) with a
> 2.0 tool-chain. Probably worked in the past because it was still 2.99
> I was using as -current (updateing only the "config" programm).

True.

> The thing that probably misguided me was that a "which genassym" in the
> compile/<name> directory ended with a no such file in $PATH.
>=20
> Though it seams from
> ftp://ftp.netbsd.org/pub/NetBSD/NetBSD-current/src/UPDATING
> that only installing /usr/bin/genassym would suffice,
>=20
> I will most likely not download the whole source tree, but stick to
> the 2.x kernel branch until a complete reinstall.
>=20
> Thanks for your assistance.

No problem.

Take care,

Bill

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

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

iD8DBQFDDnPSWz+3JHUci9cRAmiBAJ9xOFldtj1b9uxYlcam0QrmCc4w9gCfa78Z
b/2HjComibHA8fZlt+tFcYs=
=tnfL
-----END PGP SIGNATURE-----

--vOmOzSkFvhd7u8Ms--