From:	Uta Conrad <ukt AT mail DOT lrz-muenchen DOT de>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: DJGPP / DOS and Novell ??
Date:	Mon, 19 Oct 1998 16:12:15 +0100
Organization:	[posted via] Leibniz-Rechenzentrum, Muenchen (Germany)
Lines:	62
Distribution:	world
Message-ID:	<362B56CF.3E8833B2@mail.lrz-muenchen.de>
References:	<362860FF DOT 35D1166E AT mail DOT lrz-muenchen DOT de> <36290EA5 DOT 5D00C1E9 AT cartsys DOT com>
NNTP-Posting-Host:	dialb108.ppp.lrz-muenchen.de
Mime-Version:	1.0
X-Mailer:	Mozilla 4.05 [de]C-NECCK (Win95; I)
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

Nate Eldredge schrieb:
> 
> Uta Conrad wrote:
> >
> > Hi,
> >
> > I'm trying to install DJGPP in the network at our school. I now gave up
> > the installation on an Network drive because it sent me each time I
> > started the compiler a diffrent error message.
> > Installing it on the workstations seems to be better. But there is still
> > a problem compiling c++ code.
> > The compiler can't find the directory c:\djgpp\lib\g++-include which is
> > no surprise because g++-include has  more than 8 chars. The djgpp.env
> > seems to be correct (LFN=n).
> 
> Not to mention that `+' is illegal in a vanilla DOS filename.
> 
> But the deeper problem is: why is it looking for it at all?  As far as I
> know, nothing in DJGPP is stored in such a directory.  C++ headers
> belong (unless this has changed with 2.8.x (which I really need to get
> one of these days :)) in \djgpp\lang\cxx, and that's where the compiler
> should look for and find them.  Thus, please post the output of a
> failing compile using the `-v' option, and the contents of your
> environment (output of SET).
> --
> 
> Nate Eldredge
> nate AT cartsys DOT com

This is our environment:
(The Z,Y ... drives are Netware Drives) 

PROMPT=$p$g
TEMP=C:\TMP
TMP=C:\TMP
RECHNER=EVELYN
COMSPEC=C:\COMMAND.COM
NWLANGUAGE=DEUTSCH
DJGPP=c:/djgpp/djgpp.env
PATH=C:\NOVELL\CLIENT32\;C:\NWCLIENT\;C:\BAT;C:\DOS;C:\WIN;Z:.;Y:.;X:.;W:.;V:.;c:\djgpp\bin
windir=C:\WIN

And this is the output of the failing compile:

K:\PFE16>gcc -v h:\cpp\versuch.cpp
Reading specs from c:/djgpp/lib/specs
gcc version 2.8.1
 c:/djgpp/lib/gcc-lib/djgpp\2.81\cpp.exe -lang-c++ -v -undef
-D__GNUC__=2 -D__GNUG__=2 -D__cplusplus -D__GNUC_MINOR__=8 -Dunix -Di386
-DGO32 -DMSDOS -DDJGPP=2 -DDJGPP_MINOR=1 -D__unix__ -D__i386__
-D__GO32__ -D__MSDOS__ -D__DJGPP__=2 -D__DJGPP_MINOR__=1 -D__unix
-D__i386 -D__GO32 -D__MSDOS -D__DJGPP=2 -D__DJGPP_MINOR=1 -D__EXCEPTIONS
h:\cpp\versuch.cpp c:/djgpp/tmp\ccaaiune
GNU CPP version 2.8.1 (80386, BSD syntax)
h:\cpp\versuch.cpp:0: $DJDIR/lib/g++-include/.: No such device (ENODEV)
#include "..." search starts here:
#include <...> search starts here:
 c:/djgpp/include
 c:/djgpp/lib/gcc-lib/djgpp/2.81/include
 c:/djgpp/include
End of search list.
h:\cpp\versuch.cpp:1: iostream.h: No such file or directory (ENOENT)

- Raw text -