From: "Mark E." <snowball3 AT bigfoot DOT com>
To: djgpp-workers AT delorie DOT com
Date: Thu, 1 Jun 2000 20:34:37 -0400
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Subject: Binutils 2.10 and 8.3 filename clashes
Message-ID: <3936C8DD.14582.675545@localhost>
X-mailer: Pegasus Mail for Win32 (v3.12c)
Reply-To: djgpp-workers AT delorie DOT com

Binutils 2.10 isn't far away, and I wanted some advice on what to do about 
some filename conflicts reported by doschk. They don't affect building 
Binutils for DJGPP under DOS, so I'm not sure if I should risk renaming them 
(and then miss that one reference the breaks someone's cross-build) or just 
leave them be and warn appopriately.

The following resolve to the same DOS file names:
ARMELF_L.SH    : ./ld/emulparams/armelf_linux.sh
		 ./ld/emulparams/armelf_linux26.sh
AVRMEGA1.SH    : ./ld/emulparams/avrmega103.sh
		 ./ld/emulparams/avrmega161.sh
COFF-TIC.C     : ./bfd/coff-tic30.c
		 ./bfd/coff-tic80.c
ELF32-I3.C     : ./bfd/elf32-i370.c
		 ./bfd/elf32-i386.c
ELF32BMI.SH    : ./ld/emulparams/elf32bmip.sh
		 ./ld/emulparams/elf32bmipn32.sh
ELF32PPC.SH    : ./ld/emulparams/elf32ppc.sh
		 ./ld/emulparams/elf32ppclinux.sh
ELF_E_FL.D     : ./gas/testsuite/gas/mips/elf_e_flags1.d
		 ./gas/testsuite/gas/mips/elf_e_flags2.d
		 ./gas/testsuite/gas/mips/elf_e_flags3.d
		 ./gas/testsuite/gas/mips/elf_e_flags4.d
ELF_I386.SH    : ./ld/emulparams/elf_i386.sh
		 ./ld/emulparams/elf_i386_be.sh
LD-ILOCK.D     : ./gas/testsuite/gas/mips/ld-ilocks-addr32.d
		 ./gas/testsuite/gas/mips/ld-ilocks.d