Message-Id: <3.0.1.16.19980829122624.2bdf0d00@shadow.net>
Date: Sat, 29 Aug 1998 12:26:24
To: "John M. Aldrich" <fighteer AT cs DOT net>
From: Ralph Proctor <ralphgpr AT shadow DOT net>
Subject: Re: Testing DJGPP Installation
Cc: djgpp AT delorie DOT com
In-Reply-To: <35E8213D.38DC4751@cs.net>
References: <Pine DOT SOL DOT 3 DOT 91 DOT 980827121442 DOT 26553B-100000 AT mercury>
 <3 DOT 0 DOT 1 DOT 16 DOT 19980829111129 DOT 226750d4 AT shadow DOT net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Precedence: bulk

At 11:41 AM 8/29/98 -0400, you wrote:

>In such a situation, finding djgpp would require searching the entire
>hard drive (or all drives on a system), and possibly distinguishing
>between the non-djgpp GNU compiler and djgpp.  I thought of this kind of
>thing when writing DJVERIFY and decided that the best solution is to not
>even try, and let the user tell me where djgpp is installed if my
>program can't find it.

Oh yes, I would leave things as they are.
Leave any searching (gasp) to the user.

IMHO, I have always assumed the best place to begin working with DJGPP is
in DOS---
C:\djgpp and follow the readme.1st and FAQ.
Then, after getting some experience with the compilers and utilities one
might move on to other ways of installing armed with the skill acquired
working in DOS first. Just a way of looking at it, not necessarily the gospel.

Thanks for your remarks.

Ralph