--82I3+IH0IqGh5yIs
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

hi,

On Mon, Aug 25, 2003 at 04:36:17PM -0400, Jan Schaumann wrote:
>
> I see.  The problem (AFAICT after a brief look at tools.mk) is that
> MAKE_PROGRAM and MAKE do not contain the full path, but just the name
> of the exectuable.  We'd have to either provide a full path for MAKE,
> or otherwise treat it in a special way to make this work.

it's not really that difficult.  if USE_GMAKE is set, MAKE_PROGRAM does
contain the full path for MAKE.  if it's not set, we are using bmake and

 MAKE_PROGRAM=3D`${TYPE} ${MAKE} | ${AWK} '{print $$NF}'`

would do the trick (thank jlam for the hint).

> But it does seem to me that we actually do want to make sure that the
> invoked 'make' is always in fact what we think it is, and this
> approach is probably a way to achieve this.

johnny went even further and suggested moving USE_GMAKE to tools.mk as
USE_GNU_TOOLS+=3Dmake.  i think that's the way to go.


regards,

--=20
-- Lubomir Sedlacik <salo@Xtrmntr.org>                   --
--                  <salo@silcnet.org>                   --

--82I3+IH0IqGh5yIs
Content-Type: application/pgp-signature
Content-Disposition: inline

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

iD8DBQE/Sn5UiwjDDlS8cmMRAgKsAJ0fifG8ofUKIrxf5lJ814O5qXUPNwCcDoch
Zfc6fP7CzP98WNFqtuLCxNY=
=CH/i
-----END PGP SIGNATURE-----

--82I3+IH0IqGh5yIs--