--X+8siUETKMkW99st
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Wed, Jan 09, 2002 at 03:13:43PM +0000, David Laight wrote:
> Ah - now I see what is 'wrong'...
>=20
> Surely it is inappropriate to build makefs with the 'host' compiler and
> header files.

Well, only sort of. makefs wants to create file systems the kernel
supports. But if it's going to be part of the toolchain, it must
work without knowledge of the running system.

> So why is it being built, and what is it used for?

It's a handy utility to create any supported file system within a
file. (A generalization of mkisofs, in the conceptual sense.) makefs
itself isn't really the problem here, rather its something wrong in
the way the Makefile is dealing with it when it's built as part of
the (stand-alone, non-installation) toolchain.

There's a thread in tech-toolchain (beginning with Message-ID:
<20020109041513.J25417@grappa.eclipsed.net>, or
http://mail-index.netbsd.org/tech-toolchain/2002/01/09/0000.html,
though the responses haven't hit mail-index yet) about this that might
interest those troubled by it.

--=20
gabriel rosenkoetter
gr@eclipsed.net

--X+8siUETKMkW99st
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

iEYEARECAAYFAjw8axoACgkQ9ehacAz5CRoueQCfTqBP/f009m9OoasXiLARAecl
YyQAniCUbBUeXCtOQZLFvfA8qlqx2HTF
=OMUD
-----END PGP SIGNATURE-----

--X+8siUETKMkW99st--