Message-Id:	<199810211826.UAA15600@ieva06.lanet.lv>
From:	"Andris Pavenis" <pavenis AT lanet DOT lv>
To:	djgpp AT delorie DOT com
Date:	Wed, 21 Oct 1998 20:32:17 +0300
MIME-Version:	1.0
Subject:	Re: DJGPP / DOS and Novell ??
CC:	Uta Conrad <ukt AT extern DOT lrz-muenchen DOT de>
In-reply-to:	<362E0A06.1A91769F@mail.lrz-muenchen.de>
X-mailer:	Pegasus Mail for Win32 (v3.01b)
Reply-To:	djgpp AT delorie DOT com

Date sent:      	Wed, 21 Oct 1998 17:21:26 +0100
From:           	Uta Conrad <ukt AT extern DOT lrz-muenchen DOT de>
Copies to:      	djgpp AT delorie DOT com
Subject:        	Re: DJGPP / DOS and Novell ??
Send reply to:  	djgpp AT delorie DOT com

> Andris Pavenis schrieb:
> 
> > 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
> 
> 
> It seems to be a problem with the Client32 of Novell. I now tried to
> install the same thing without the novell-client running. It works
> fine..
> When I start the Novell client again it's the same problem again. The
> novell DOS redirector seems to confuse the gcc. Is there any chance to
> find out why this happens?
> 

I think only real cure to avoid this problem with Novell is to patch 
cccp.c (in sources of gcc-2.8.1) and rebuild gcc. 

So with official version of DJGPP port of gcc-2.8.1 we have following
problems:

	- problem with $DJDIR/lib/g++-include discussed in this thread

      - problem with Fortran runtime libraries (binary files opened in
        ASCII mode) discussed in DJGPP mailing list in June (if
        remeber correctly)

Perhaps if I'll rebuild gcc-2.8.1 for DJGPP I'll use DJGPP-2.02 
(alpha). My experience shows that egcs-1.1 I build using this alpha
version in begin of September is stable enough. So we can expect 
the same with gcc-2.8.1 (I hope)

Andris

- Raw text -