This is the mail archive of the
cygwin@sources.redhat.com
mailing list for the Cygwin project.
RE: glibc cross-compilation: file names problems
- To: "Fabrice Gautier" <gautier at email dot enst dot fr>,<cygwin at sources dot redhat dot com>
- Subject: RE: glibc cross-compilation: file names problems
- From: "Robert Collins" <robert dot collins at itdomain dot com dot au>
- Date: Fri, 2 Feb 2001 11:09:04 +1100
- Thread-Index: AcCMq8Y3iBcvAp32TlGYRQTp8XwOdQAADhPw
- Thread-Topic: glibc cross-compilation: file names problems
Cygwin depends on the windows file system interface, which is case
preserving, as opposed to case sensitive.
While you might be able to design a reversible name mangling system that
cygwin could use, I doubt it would be a) very efficient or b) easy to
implement without opening a can of worms.
So you are correct the solution is to fix the glibc makefiles.
Rob
> -----Original Message-----
> From: Fabrice Gautier [mailto:gautier@email.enst.fr]
> Sent: Friday, 2 February 2001 10:53 AM
> To: cygwin@sources.redhat.com
> Subject: glibc cross-compilation: file names problems
>
>
> Hi,
>
> I've tried to cross compile glibc from cygwin but I ran into
> some errors.
>
> i've trackeed the error done to a file name problem:
> Glibc uses *.oS and *.os temporary files during the build
> (for 's'hared
> and 'S'tatic objects)
>
> But with cygwin this files are the same, so things are not going well.
>
> I think the only solution is to change glibc makefiles, but is this a
> "classic" problem that people run into when trying to port programs to
> cygwin? Is there eventually a way to force Windows to accept two
> filename identical except for the case?
>
> (please note : i'm not trying to "port" glibc for cygwin, i'm
> just trying
> to cross compile it)
>
> Thanks
>
> --
> Fabrice Gautier <gautier@email.enstfr>
>
>
> --
> Want to unsubscribe from this list?
> Check out: http://cygwin.com/ml/#unsubscribe-simple
>
>
--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple