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

hi,

On Mon, Aug 25, 2003 at 01:52:10PM -0400, Jan Schaumann wrote:
> "Jeremy C. Reed" <reed@reedmedia.net> wrote:
> > On Mon, 25 Aug 2003, Jan Schaumann wrote:
> >=20
> > > Patch Makefiles to use @MAKE@, which then, after patching, is
> > > substituted with the actual ${MAKE} (can't use "MAKE=3D ${MAKE} -f
> > > Makefile.ssl").
> >=20
> > Thanks for doing this.
> >=20
> > I haven't looked at your patches. But maybe this is the same as my
> > PR #22509.
>=20
> Actually, yes.  I just closed that PR.  JFTR: Using tools.mk didn't
> seem suitable to me, as we do not want to artificially depend on GNU
> make.

you seem to misread the comment.  i was suggesting to link
${MAKE_PROGRAM}, not GNU make.  that is, provide an appropriate "make"
for the package in the $PATH.  it doesn't matter whether is it GNU make
or bmake, the dependency is handled way before we get to this point.
this would solve all such issues without dozens of patches.

regards,

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

--08ATZu8fEq0x2T3M
Content-Type: application/pgp-signature
Content-Disposition: inline

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

iD8DBQE/Sk8iiwjDDlS8cmMRAmqZAJ9kC2f4JXLnl22SDDE+uEQQNJURYQCfYzFc
v6kEa2HvtxhITlwVEqSB7ig=
=ZX1S
-----END PGP SIGNATURE-----

--08ATZu8fEq0x2T3M--