Re: case-sensitive file names during build

From: Pragnesh Sampat
Date: Thu Jul 22 2004 - 14:30:13 EST

> > I maintain patches that allow building glibc on Cygwin and MacOSX.
> > The main patch deals with exactly this issue (S vs. s)
> >
> -2.3.2-cygwin.patch
> > I have to maintain it separately as the glibc maintainer dislikes the
> > idea of catering to Cygwin users (though maybe if I present it as a
> > MacOSX support patch he'd reconsider... naaah, probably not :-).
> >
> > With the advent of linux-2.6, I also have a patch to get kconfig to
> > not use shared libraries (since I use kconfig to help install the
> > kernel headers, and shared libraries are tricky to build on those two
> > platforms).
> >
> > It wouldn't be a big leap for me or someone else to also maintain a
> > patch to allow compiling the whole kernel on Cygwin or MacOSX.
> > If anyone puts it together, I'll carry it in crosstool.


We have some patches that we use at TimeSys that allow a linux kernel to
build on cygwin. They fall under:

1. case insensitive issues
2. kconfig using shared library
3. header file issues under some cygwin versions (typically types.h)
4. arguments handling limited to 32K (large number of modules are issues
in Makefiles)

1 and 2 have already been discussed and Chris Faylor mentioned just a
while ago that with managed mounts under newer cygwin versions, this is
not a big issue for cygwin at least.

Sometime later today, I will send in the patches we are using for 2.6.6
that allow a full build, in case they are useful (at least the arguments
handling patch is a kludge, but I will send it in to start with).


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at