public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Michael S. Zick <mszick@goquest.com>
To: DJ Delorie <dj@redhat.com>
Cc: gcc@gcc.gnu.org
Subject: Re: Old bug: the 14-character limit.
Date: Sat, 24 May 2003 02:19:00 -0000	[thread overview]
Message-ID: <03052321064100.01644@wolf686> (raw)
In-Reply-To: <200305232053.h4NKrKZ16422@greed.delorie.com>

On Friday 23 May 2003 03:53 pm, DJ Delorie wrote:
> > Is there a documented upper limit on file name length for the gcc tree?
>
> I don't know of any hard limits, but as long as files are unique in
> the 8.3 characters (i.e. first 8 characters of the basename, first 3
> characters of the extension), even DJGPP won't care about the length.
>
> IIRC Windows has a hard upper limit on total path size, but I forget
> what it is.  DJGPP's MAXPATH is 260 (for LFN; 80 for SFN), which is
> probably related to the Windows limit.
Some GNU/Linux systems use:

[root@wolf686 mszick]# stat -f /dev/hda
  File: "/dev/hda"
    ID: 0        0        Namelen: 255     Type: EXT2

  parent reply	other threads:[~2003-05-24  2:14 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
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   ` Mike Stump
2003-05-23 20:53   ` Phil Edwards
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 [this message]
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=03052321064100.01644@wolf686 \
    --to=mszick@goquest.com \
    --cc=dj@redhat.com \
    --cc=gcc@gcc.gnu.org \
    /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).