--Xm/fll+QQv+hsKip
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Fri, Oct 03, 2003 at 01:50:44PM -0600, Rick Kelly wrote:
> Perry E. Metzger said:
>=20
> >Strange. My (very vanilla) build.sh runs are having no trouble
> >whatsoever.
>=20
> I believe my problems stem from the fact that it is trying to cross-compi=
le
> for itself. My other -current box, running SMP kernel, built fine after I
> hand built gcc3.
>=20
> Differences:
>=20
> Problem box: running circa 1.6P userland and 1.6ZC kernel. Compiler is
> gcc3 built by hand (also g++3 and all need gnu libraries). The build
> system believes it is cross-compiling NetBSD.
>=20
> Other box: was running bits from 9/9/2003, pre-gcc3. I built the compiler
> by hand, and got a complete build with the only problems being some kernel
> nits in the CVS repository. Did not do the build as a cross-compile.
>=20
> Perhaps the problem box could build if I knew what the steps were for
> cross-compiling.

build.sh is supposed to alway cross-build, even to same CPU.

--Xm/fll+QQv+hsKip
Content-Type: application/pgp-signature
Content-Disposition: inline

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

iD8DBQE/fkhVWz+3JHUci9cRArNgAJ99ePk5avpD2iFORSZv4GmtYjugEQCdHTBr
QdwBR3v7bVP31haOqu9V8hM=
=dtrw
-----END PGP SIGNATURE-----

--Xm/fll+QQv+hsKip--