> From: Espen Ottar <espen.ot...@greendigital.no>
> Date: Mon, 30 Jun 2025 07:47:41 +0000
>
> On Windows it is possible to enable case sensitivity on a per-folder basis .
> (using fsutil.exe)
> When case sensitivity is enabled, make fails to read "Makefile" (with capital
> M)
> The workaround is to use "make -f Makefile" but that should not be necessary
I cannot reproduce this with GNU Make 4.4.1 built for native Windows.
Which port of GNU Make are you using and where did you download it
from?
The source code clearly shows that the MS-Windows port does look for
Makefile:
/* If there were no -f switches, try the default names. */
if (num_makefiles == 0)
{
static const char *default_makefiles[] =
#ifdef VMS
/* all lower case since readdir() (the vms version) 'lowercasifies' */
/* TODO: Above is not always true, this needs more work */
{ "makefile.vms", "gnumakefile", "makefile", 0 };
#else
#ifdef _AMIGA
{ "GNUmakefile", "Makefile", "SMakefile", 0 };
#else /* !Amiga && !VMS */
#ifdef WINDOWS32
{ "GNUmakefile", "makefile", "Makefile", "makefile.mak", 0 };
#else /* !Amiga && !VMS && !WINDOWS32 */
{ "GNUmakefile", "makefile", "Makefile", 0 };
#endif /* !Amiga && !VMS && !WINDOWS32 */
#endif /* AMIGA */
#endif /* VMS */
const char **p = default_makefiles;
while (*p != 0 && !file_exists_p (*p))
++p;
As you see, it tries "makefile", and then tries Makefile if makefile
doesn't exist.
If this is not what you see, please post a complete recipe for
reproducing the problem, including the command(s) you used to make a
directory case-sensitive for file names, the command(s) you used to
create a Makefile and the command you use to run Make.
