From: Phil Edwards <phil@jaj.com>
To: Laurent GUERBY <guerby@acm.org>
Cc: Nathanael Nerode <neroden@twcny.rr.com>, gcc@gcc.gnu.org
Subject: Re: Old bug: the 14-character limit.
Date: Fri, 23 May 2003 20:53:00 -0000 [thread overview]
Message-ID: <20030523204823.GA2713@disaster.jaj.com> (raw)
In-Reply-To: <1053721320.3886.43.camel@localhost.localdomain>
On Fri, May 23, 2003 at 10:22:01PM +0200, Laurent GUERBY wrote:
> According to my experiments, the longest file name in the gcc source
> tree is 48 characters: gnu_java_awt_peer_gtk_GtkCheckboxMenuItemPeer.c
> in libjava/jni/gtk-peer/.
Like DJ said, we don't care about name length for building, only for
installing, and most of us don't even care very much about that. :-)
> Is there a documented upper limit on file name length for the gcc tree?
> If not is there a common wisdom upper limit?
Some versions of (non-GNU) tar have a 100-char limit on certain names.
--
If ye love wealth greater than liberty, the tranquility of servitude greater
than the animating contest for freedom, go home and leave us in peace. We seek
not your counsel, nor your arms. Crouch down and lick the hand that feeds you;
and may posterity forget that ye were our countrymen. - Samuel Adams
next prev parent reply other threads:[~2003-05-23 20:48 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 [this message]
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=20030523204823.GA2713@disaster.jaj.com \
--to=phil@jaj.com \
--cc=gcc@gcc.gnu.org \
--cc=guerby@acm.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).