public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: DJ Delorie <dj@redhat.com>
To: neroden@twcny.rr.com
Cc: gcc@gcc.gnu.org
Subject: Re: Old bug: the 14-character limit.
Date: Fri, 23 May 2003 19:52:00 -0000	[thread overview]
Message-ID: <200305231951.h4NJpZW15256@greed.delorie.com> (raw)
In-Reply-To: <20030523193958.GA12758@doctormoo> (message from Nathanael Nerode on Fri, 23 May 2003 15:39:58 -0400)


> 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.

  reply	other threads:[~2003-05-23 19:51 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-23 19:41 Nathanael Nerode
2003-05-23 19:52 ` DJ Delorie [this message]
2003-05-25 18:17   ` Andris Pavenis
2003-05-23 20:44 ` Laurent GUERBY
2003-05-23 20:45   ` Neil Booth
2003-05-23 20:53   ` Phil Edwards
2003-05-23 20:53   ` Mike Stump
2003-05-23 20:54   ` DJ Delorie
2003-05-23 21:34     ` Laurent GUERBY
2003-05-23 21:53       ` DJ Delorie
2003-05-24  9:27         ` Laurent GUERBY
2003-05-24 14:23           ` DJ Delorie
2003-05-24  2:19     ` Michael S. Zick
2003-05-23 19:44 Nathanael Nerode

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200305231951.h4NJpZW15256@greed.delorie.com \
    --to=dj@redhat.com \
    --cc=gcc@gcc.gnu.org \
    --cc=neroden@twcny.rr.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).