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

On Sun, Jul 23, 2006 at 10:09:38, Garrett D'Amore wrote:
> That is quite strange.  Others have been building com(4) for a while
> since the relevant changes were made, without difficulty.
>=20
> How are you building?  Are you using build.sh or something else?

$ env HAVE_GCC=3D3 ./build.sh -u -U -O ../obj -T ../obj/tooldir.* kernel=3D=
ENCANTA

> Are you working with a complete source tree?  The fresh checkout
> should be fine.

Yes - a full checkout of src/.  As it turns out I don't actually need
com(4) drivers, I can build by pulling them out of my config - not
really a definitive solution to the problem, though it suffices for me.

--=20
  .oliver

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

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

iD8DBQFExaJ7NtBooygWxWcRAvLYAJwKguD7nhM5GxFe68INfQUtalMedgCg7Nh1
HnmafL94AJPYqB40PkmViSM=
=cb/J
-----END PGP SIGNATURE-----

--d6Gm4EdcadzBjdND--