Maybe it is not a bug, as I already indicated in my OP. The fact that it behaves different than 3.81 used to is "the regression". Maybe the change just fixes a bug in 3.81 and the behavior of 4.x is how it should have worked all along, it's just a matter on how you look at it.
-----Original Message----- From: Eli Zaretskii <[email protected]> Sent: Friday, 21 May 2021 4:18 PM To: Ronald Hoogenboom <[email protected]> Cc: [email protected]; [email protected] Subject: Re: basename function in 4.3 cygwin > From: Ronald Hoogenboom <[email protected]> > CC: "[email protected]" <[email protected]> > Date: Fri, 21 May 2021 13:57:49 +0000 > Accept-Language: en-US > > 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. What is the regression? can you show an example that can be reproduced and analyzed? The native Windows port of GNU Make interprets backslashes as directory separators, as expected. If this is what you see, it isn't a bug.
