[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: GNU Make 4.4.0.91 on Cygwin
From: |
Eli Zaretskii |
Subject: |
Re: GNU Make 4.4.0.91 on Cygwin |
Date: |
Mon, 20 Feb 2023 14:47:36 +0200 |
> From: Paul Smith <psmith@gnu.org>
> Date: Sun, 19 Feb 2023 14:59:35 -0500
>
> On Sun, 2023-02-19 at 20:32 +0100, Bruno Haible wrote:
> > All "Device or resource busy" failures are gone. Only the 1 failure
> > in category 'misc/general4' is still present.
>
> Hm. This is a test of this:
> https://savannah.gnu.org/bugs/index.php?57674
>
> which explicitly removes PATH from the environment completely. It
> should use a default PATH, which should mean "echo" works even so. I'm
> not really sure how this should react on a cygwin system, but I guess
> since it behaves properly on Windows and POSIX it should work on cygwin
> as well. I'll have to figure out why only cygwin isn't working.
How do you conclude that this "works on Windows"? In my testing, it
doesn't, and I therefore disable this test on Windows:
# SV 57674: ensure we use a system default PATH if one is not set
# This cannot work on MS-Windows, because PATH is used to find
# shared libraries against which Make was built.
if ($port_type ne 'W32') {
delete $ENV{PATH};
run_make_test(q!
a: ; @echo hi
!,
'', "hi\n");
}
Maybe it could work if you link Make statically, or if you copy the
dependency DLLs into a system directory where Windows looks regardless
of PATH. But in general, emptying PATH on Windows is not very useful.