Message-Id: <200008101619.MAA10362@delorie.com> Date: Thu, 10 Aug 2000 19:15:28 +0200 To: gautier DOT demontmollin AT maths DOT unine DOT ch X-Mailer: Emacs 20.6 (via feedmail 8.2.emacs20_6 I) and Blat ver 1.8.5b From: "Eli Zaretskii" CC: djgpp AT delorie DOT com In-reply-to: <3992A575.DD7D7B9D@maths.unine.ch> (message from Gautier on Thu, 10 Aug 2000 14:52:04 +0200) Subject: Re: DJGPP neither running on ms-dos 6.2 nor on caldera-dos 7.03 References: <3992A575 DOT DD7D7B9D AT maths DOT unine DOT ch> Reply-To: djgpp AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: djgpp AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk > Date: Thu, 10 Aug 2000 14:52:04 +0200 > From: Gautier > > The name crunching algorithm of GNAT is completely automatic, following > precise rules (with the exception of "a-", "g-" etc. for standard packages). I understand that. However, such a feature must be added to the official GCC distribution, for us to be able to rely on it. In addition, when you say "make install", the package should automatically rename the long file names to their ``crunched'' equivalents, so that you could build the package on LFN platforms for use with DJGPP. (Alternatively, the renaming could be done right after unpacking the source distribution, before it is built.) Without all this being done automatically, such a feature is not really useful, even though the technology is simple and proven. (FWIW, right now, GCC cannot even be unpacked, let alone built, on a non-LFN platform.) > As for the compilers's behaviour, it is very simple: if a source > uses SVGA.Effects, the compiler will search for the file svgaeffe.ads > as Krunch tells it, for SVGA.Effects.IO, it will look for svgeffio.ads > and nothing else Note that, while this is a good approach, it still has its drawbacks. For example, someone might bring an LFN-named version of a file (e.g. from another platform), but will be unable to use it before renaming it. I think it is better to look for both long and short names. However, this usually needs quite a bit of heuristic code; see gxx.c in djlsr203.zip for an example.