I checked the native windows port of gnu-make I have (x86_64-pc-msys, version 4.2.1) and it exhibits the same behavior as what I see on cygwin. Apparently this is not cygwin specific.
Since you state that there were some changes done between 3.81 and 4.x with regards to the backslash path separator, I guess that is what caused this regression. -----Original Message----- From: Eli Zaretskii <[email protected]> Sent: Friday, 21 May 2021 3:45 PM To: [email protected] Cc: Ronald Hoogenboom <[email protected]>; [email protected] Subject: Re: basename function in 4.3 cygwin > From: Paul Smith <[email protected]> > Date: Fri, 21 May 2021 09:34:47 -0400 > > On Fri, 2021-05-21 at 08:31 +0000, Ronald Hoogenboom wrote: > > I have noticed a nasty difference in behavior between 4.3 and 3.81 > > versions of gnu-make in cygwin. > > > > I’m not sure if this qualifies as a bug per-se, but it is a nasty > > difference in behavior anyway. At least this should be documented in > > the info file. > > We don't develop or support (or document) the cygwin port of GNU make > on this list. If you can reproduce this behavior on the native > Windows port of GNU make (see the README.W32 for how to build it) then > we will definitely want to fix it. > > If it is only reproducible in the cygwin port but not the native > Windows port, please file an issue with the Cygwin development team. FWIW, I'd actually expect it to be the other way around: to hear that Make 3.81 considered a backslash to be a directory separator, whereas Make 4.3 did not. That's because some years ago the Cygwin developers decided they want no longer support native MS-Windows file names, only Posix- style file names. But other than that, I agree with Paul: this should probably be taken up with the Cygwin developers through their mailing list.
