Re: Potential spiped 1.4.0 release -- please test

To: Colin Percival <cperciva@tarsnap.com>

Subject: Re: Potential spiped 1.4.0 release -- please test

From: Frederick Akalin <akalin@gmail.com>

Date: Sat, 30 Aug 2014 12:24:36 -0700

In-reply-to: <00000148285a56ba-a6bae5fa-9858-4139-871f-615786607a09-000000@email.amazonses.com>

References: <CAN6O4Kr5SiLEt4X+aM-P=U5cEauo4pfK9iOC1BCidSFfA9a13Q@mail.gmail.com> <53F9811F.8080300@tarsnap.com> <CAC0aHXZcmpJwZKiFEFm1XXrj6q09fB_tVrCXxh0JqsuEFB96JA@mail.gmail.com> <00000148285a56ba-a6bae5fa-9858-4139-871f-615786607a09-000000@email.amazonses.com>

On Sat, Aug 30, 2014 at 12:18 PM, Colin Percival <cperciva@tarsnap.com> wrote:

I don't assume that make is bsdmake, only that it is something POSIX-compliant.
But you're right that I should use ${MAKE}, in case it isn't in the path. (I
don't know if anyone actually gets this right, but if make is not in the path
and is invoked via /path/to/make, then ${MAKE} should be "/path/to/make" and
not just "make".)

My mistake, I confused the release Makefile with the one used during normal development (i.e., the one in the repository). I'm running into some additional errors with that one -- will send out a separate post when I figure them out.

Can you try the attached patch?

Works for me (with both make and bsdmake)! Thanks.

-- Fred