Message-Id: <5.1.0.14.0.20020730102740.00bf1cf8@pop.inbox.lv>
X-Sender: jlsgarrido AT mail DOT SoftHome DOT net
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Tue, 30 Jul 2002 10:30:23 -0500
To: djgpp AT delorie DOT com
From: "J. L." <jlsgarrido AT SoftHome DOT net>
Subject: Re: Problem installing DJGPP package
In-Reply-To: <ai5oio$j0i$1@nets3.rz.RWTH-Aachen.DE>
References: <5 DOT 1 DOT 0 DOT 14 DOT 0 DOT 20020729180059 DOT 00ba55c8 AT imss DOT gob DOT mx>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
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

At 10:08 a.m. 30/07/2002 +0000, you wrote:

 >> Where is recommended this thing?

 > The recommendation covers what lines to put into DJGPP.bat, and the
 > idea to have it in a separate file rather than directly in
 > autoexec.bat has been issued in this newsgroup several times.  In a
 > nutshell: if you have other C development packages besides GCC
 > installed on your system, chances are that no single fixed setup of
 > environment variables will allow them all to operate.  Editing
 > autoexec.bat in the way described by readme.1st will break operation
 > of those other compilers, and re-installing them is likely to break
 > DJGPP.  That's where having "prepare compiler XYZ to be used" .bat
 > files becomes useful, if not strictly necessary.

Thanks for the info.

 > --
 > Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de)
 > Even if all the snow were burnt, ashes would remain.

J. L: