This is the mail archive of the
gcc-prs@gcc.gnu.org
mailing list for the GCC project.
Re: libgcj/2388: Problems on cygwin. Case insensitive file system?
- To: nobody at gcc dot gnu dot org
- Subject: Re: libgcj/2388: Problems on cygwin. Case insensitive file system?
- From: Tom Tromey <tromey at redhat dot com>
- Date: 31 Mar 2001 02:36:00 -0000
- Cc: gcc-prs at gcc dot gnu dot org,
- Reply-To: Tom Tromey <tromey at redhat dot com>
The following reply was made to PR libgcj/2388; it has been noted by GNATS.
From: Tom Tromey <tromey@redhat.com>
To: David.Billinghurst@riotinto.com
Cc: gcc-gnats@gcc.gnu.org
Subject: Re: libgcj/2388: Problems on cygwin. Case insensitive file system?
Date: 30 Mar 2001 19:42:48 -0700
>>>>> "David" == David Billinghurst <David.Billinghurst@riotinto.com> writes:
David> After adding libffi support for win32 (using the patches posted
David> in January) I see the following, which seems to be due to case
David> a insensitive file system.
There are definitely problems here :-(.
I don't know if this particular bug is caused by the problems, but
there are other similar problems lurking.
For instance consider the code in check_class_interface_creation()
that uses strncmp to compare an interface name against a file name.
This is incorrect on Windows.
There's some similarly failing code in note_possible_classname() and
add_entry(). You can find more in parse.y by looking for the regexp
`strn?cmp'.
Unfortunately, while some work has been done porting gcj and libgcj to
Windows, the support hasn't really been kept up.
We'd love to have somebody work on this. If you're interested and
motivated, we'd welcome your help -- if so tell me what I can do to
ease your way.
If you can't do it, that's fine, but it means you'll just have to wait
for somebody who can do it.
Tom