This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Old bug: the 14-character limit.
- From: DJ Delorie <dj at redhat dot com>
- To: neroden at twcny dot rr dot com
- Cc: gcc at gcc dot gnu dot org
- Date: Fri, 23 May 2003 15:51:35 -0400
- Subject: Re: Old bug: the 14-character limit.
- References: <20030523193958.GA12758@doctormoo>
> Are we still trying to preserve 14-character/8.3 uniqueness for
> building GCC (at least for C; C++ and Java libraries have other
> standards)? I was under the impression that we were, but I couldn't
> find it documented anywhere.
I don't think there are any old SYSV systems still around that have
the 14 character limit.
For DJGPP (the one remaining 8.3 system), we've accepted the fact that
an LFN-capable system is required for building, but still require 8.3
compatibility in the *installed* files (i.e. you need LFN to build,
but not to use). This includes C++ and Java.
Note that all Microsoft-based systems also have case-insensitive file
systems, so things like String.h and string.h are the same file.
The FSF has a program called "doschk" that can scan for potential file
name conflicts.