This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Case-insensitive filesystem problem with current CVS
- To: "gcc at gcc dot gnu dot org" <gcc at gcc dot gnu dot org>
- Subject: Case-insensitive filesystem problem with current CVS
- From: "R. Kelley Cook" <Kelley dot Cook at home dot com>
- Date: Fri, 15 Dec 2000 08:45:23 -0500
- Reply-To: "R. Kelley Cook" <Kelley dot Cook at home dot com>
When updating the current gcc CVS under cygwin, I was getting some
"in the way" errors. So I deleted the files in question and tried again:
$ mv gcc/texinfo.sav gcc/texinfo; cvs -z 9 -q -d :pserver:anoncvs@gcc.gnu.org:/cvs/gcc update -Pd;
mv gcc/texinfo gcc/texinfo.sav
? gcc/texinfo/texinfo.sav
U gcc/gcc/configure
M gcc/gcc/system.h
U gcc/libffi/src/mips/ffi.c
U gcc/libffi/src/mips/n32.S
cvs update: move away gcc/libffi/src/mips/n32.s; it is in the way
C gcc/libffi/src/mips/n32.s
U gcc/libffi/src/mips/o32.S
cvs update: move away gcc/libffi/src/mips/o32.s; it is in the way
C gcc/libffi/src/mips/o32.s
Took me a bit to actually notice what was going on, but there are {n,o}32.s
as well as {n,o}32.S (Notice the capitalization difference in the extension)
This unfortunately will not work very well in multitude of case-insensitive
filesystems out there. Two of those files should be renamed.