From: DJ Delorie <dj@redhat.com>
To: guerby@acm.org
Cc: gcc@gcc.gnu.org
Subject: Re: Old bug: the 14-character limit.
Date: Sat, 24 May 2003 14:23:00 -0000 [thread overview]
Message-ID: <200305241411.h4OEB4J20365@greed.delorie.com> (raw)
In-Reply-To: <1053767326.3886.101.camel@localhost.localdomain> (message from Laurent GUERBY on 24 May 2003 11:08:47 +0200)
> - As far as we're not too far from 100 (portential tar limit) or 250
> characters (more common limit on modern file systems)
> for files needed during the build, and that includes DJGPP, right?
> (I don't know DJGPP, so I assume there's some distinction
> between build and use once installed.)
Yes. The thing about DJGPP is it supports two filesystem APIs, "short
file names" (SFN, or 8.3) and "long file names" (LFN). Not all
Windows OSs provide LFN services, and some DOS systems have LFN
drivers. In general, though, it's acceptable to require that someone
BUILDING a gnu package make the effort to obtain LFN services.
> - If one wants to install a compiler on a platform, 8+3 name
> uniqueness for all files to be installed is required for the
> compiler to be useable under the DJGPP platform.
Yes, because for USING a gnu package it is unacceptable to require LFN
services. Dosemu, for example, cannot provide them for a shared linux
partition.
next prev parent reply other threads:[~2003-05-24 14:12 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 [this message]
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=200305241411.h4OEB4J20365@greed.delorie.com \
--to=dj@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=guerby@acm.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).