From: Hans-Bernhard Broeker <broeker AT physik DOT rwth-aachen DOT de>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Problems with Loader Error
Date: 25 Apr 2000 12:03:42 GMT
Organization: Aachen University of Technology (RWTH)
Lines: 27
Message-ID: <8e41iu$9eo$1@nets3.rz.RWTH-Aachen.DE>
References: <20000420180610 DOT 97856 DOT qmail AT hotmail DOT com> <200004210744 DOT DAA16985 AT indy DOT delorie DOT com>
NNTP-Posting-Host: acp3bf.physik.rwth-aachen.de
X-Trace: nets3.rz.RWTH-Aachen.DE 956664222 9688 137.226.32.75 (25 Apr 2000 12:03:42 GMT)
X-Complaints-To: abuse AT rwth-aachen DOT de
NNTP-Posting-Date: 25 Apr 2000 12:03:42 GMT
Originator: broeker@
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

Eli Zaretskii <eliz AT delorie DOT com> wrote:
>> From: "Paul Edwards" <bin_kicker AT hotmail DOT com>
[...]
>> Loader Error (0025): cannot initialise.

> This is a telltale sign of a Borland cpp.exe sitting on your PATH
> before DJGPP's version. 
[...]
> Solution: change your PATH so that DJGPP's bin subdirectory appears
> before Borland's.

That solution has a drawback, though: now Borland's compiler will
probably choke. Not because of DJGPP's cpp.exe (it doesn't use
standalone cpp, IIRC), but because of DJGPP's make.exe shadowing their
make.exe in the PATH.

A better solution thus is to make sure that at any time, only *one*
compiler package is in the PATH. Depending on whether you're using DOS
or Windows, you can either have a series of batch files that set up
and delete the environment variables, including PATH, for each
compiler, and switch back and forth by calling one of them; or you can
set up separate DOS-box shortcuts in Windows, each with a different
startup batch file.

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