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

On Wed, Mar 10, 2004 at 08:38:11AM +0000, Nick Hudson wrote:
  | It seems to me that this can be avoided by introducing a new HAVE_PIC
  | variable that is defined by the platform.=20
  |=20
  | 	MKPIC?=3D	${HAVE_PIC}
  |=20
  | Other candidates for HAVE_* variables are
  |=20
  | 	HAVE_EXTERNAL_TOOLCHAIN	replaces defined(EXTERNAL_TOOLCHAIN)
  | 	HAVE_GCC3		already exists
  | 	HAVE_GDB		for MKGDB
  | 	HAVE_LINT		for MKLINT
  | 	HAVE_PIC		for MKPIC
  | 	HAVE_PICLIB		for MKPICLIB
  | 	HAVE_PROFILE		for MKPROFILE
  |	HAVE_TOOLCHAIN		replaces TOOLCHAIN_MISSING; global
  | 				control for stuff like GCC3, GDB, ...
  |=20
  | Thoughts?

I like it (partially because I came up with those names in private
discussion with you ;-)

(I asked Nick to sanity check the idea here on tech-toolchain)

--1LKvkjL3sHcu1TtY
Content-Type: application/pgp-signature
Content-Disposition: inline

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

iD8DBQFAUHXUpBhtmn8zJHIRAnHmAKClRWtA7uEBrt09CIKDa7Cl9mccNQCgqVu4
OKBm3Lj5zb7Jxi/1fYC+X/I=
=2udH
-----END PGP SIGNATURE-----

--1LKvkjL3sHcu1TtY--