On Sat, Sep 21, 2019 at 04:54:59PM -0400, Paul Smith wrote:
> I pushed a different fix for this issue. Thanks for noticing!
Thank you.
Do you intentionally avoid $! in the "Cannot execute" error message?
regards, Dmitry
>
___
Bug-make mailing list
Bu
On Wed, 2019-09-18 at 21:38 -0400, Dmitry Goncharov via Bug reports and
discussion for GNU make wrote:
> The test suite fails to run valgrind with an error message like the following.
I pushed a different fix for this issue. Thanks for noticing!
___
B
Update of bug #56918 (project make):
Status:None => Fixed
Open/Closed:Open => Closed
Fixed Release:None => SCM
Triage Status:
On Sat, 2019-09-21 at 12:09 -0700, Paul Eggert wrote:
> On 9/21/19 10:55 AM, Paul Smith wrote:
> > perl -we 'use File::Spec; my @o = File::Spec->splitpath("../make");
> > print "@o\n"'
>
> It outputs a single line containing " ../ make".
>
> Hmm, I already wrote that, in one of my comments here:
On 9/21/19 10:55 AM, Paul Smith wrote:
perl -we 'use File::Spec; my @o = File::Spec->splitpath("../make"); print
"@o\n"'
It outputs a single line containing " ../ make".
Hmm, I already wrote that, in one of my comments here:
https://lists.gnu.org/r/bug-make/2019-09/msg00101.html
Perhaps you
On Mon, 2019-09-16 at 15:49 -0400, Paul Smith wrote:
> Ugh, that's wrong. It should be " ../ make" (note the space before
> "make"). File::Spec is not correctly splitting the directory from the
> file, apparently. Bogus!! Can you try this one:
>
> perl -we 'use File::Spec; my @o = File::Spec
