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

On Thu, Feb 24, 2005 at 10:13:51AM -0800, John Klos wrote:
> >>cc    -O -DIN_GCC -DCROSS_COMPILE  -W -Wall -Wwrite-strings
> >>-Wstrict-prototypes -Wmissing-prototypes -Wtraditional -pedantic
> >>-Wno-long-long   -DHAVE_CONFIG_H -DGENERATOR_FILE  -o gengtype  gengtyp=
e.o
> >>gengtype-lex.o gengtype-yacc.o ../libiberty/libiberty.a
> >>nbmake: don't know how to make
> >>/usr/src/tools/gcc/../../gnu/dist/gcc/gcc/fold-const.c. Stop
> >>
> >>nbmake: stopped in /usr/obj/tools/gcc/build/gcc
> >
> > AFAIK, using non-gnumake to build GCC isn't supported.
>=20
> So when / how did this get changed and broken in 2.0? Has it always been=
=20
> not supported?

Oh... no, we build with nbmake, when using our toolchain and our source-tre=
e.
This should work, but I must admit that I didn't test it natively on m68k
for a long time.... I prefer cross-building.

	-is

--=20
seal your e-mail: http://www.gnupg.org/

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

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

iD8DBQFCHlI6N4tiz3B8hB0RAsbXAJ9N+xnDtVekRk+Z93T3wCc2fQ/zUACglIMm
coeRsJ9+U+HJ5HIvrTGz+K4=
=h9Dw
-----END PGP SIGNATURE-----

--rwEMma7ioTxnRzrJ--