Date: Tue, 20 Oct 1998 10:18:27 +0200 (WET)
From: Andris Pavenis <pavenis AT lanet DOT lv>
To: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
cc: Uta Conrad <ukt AT mail DOT lrz-muenchen DOT de>, djgpp AT delorie DOT com
Subject: Re: DJGPP / DOS and Novell ??
In-Reply-To: <Pine.SUN.3.91.981019172229.12098I-100000@is>
Message-ID: <Pine.A32.3.91.981020100337.38830A-100000@ieva05.lanet.lv>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp AT delorie DOT com



On Mon, 19 Oct 1998, Eli Zaretskii wrote:

> 
> On Mon, 19 Oct 1998, Uta Conrad wrote:
> 
> > 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)
> 
> I think there's something wrong with your setup: the search path for C++ 
> include files should have included c:/djgpp/lang/cxx.  Are you using the 
> stock DJGPP.ENV file that came with djdev201.zip, or did you edit it in 
> some way?
> 
> In addition, I don't understand the message about ``no such device''.  
> One possible reason for it might be that you edited DJGPP.ENV to 
> put there the string that begins with $DJDIR.
> 
> Andris, do you have any additional ideas why could such a message be 
> printed?
> 

Looks like bug in DJGPP port of gcc together with problem outside gcc.
cpp.exe should substitute $DJDIR in $DJDIR/lib/g++-include similary 
as it is done with $DJDIR/lang/cxx. Unfortunatelly this does not happen
with both gcc-2.8.1 and egcs-1.1 I have tested. You can verify this
with following steps (under Win9X with LFN support enabled but NOT from 
bash to prevent expansion of $DJDIR)
	touch test.cc
	mkdir $DJDIR
        mkdir $DJDIR/lib
	mkdir $DJDIR/lib/g++-include
	gcc -c -v test.cc
I have thought about removing lookup in $prefix/lib/g++-include for DJGPP
port of gcc as it also potentially can cause problems in cross-compiling
(I have met them under Linux)

But anyway this problem alone should not do any harm. Perhaps there is
additional problem (perhaps with Novell) that trying to read contents
of that non existant directory with wrong DOS name some weird error 
code is returned. I cannot study it more detailed as I'm not using Novell 
netware.

Andris