Message-Id:	<199804061246.OAA10454@crimson.ihg.uni-duisburg.de>
From:	michael DOT mauch AT gmx DOT de (Michael Mauch)
To:	Robert Hoehne <robert DOT hoehne AT gmx DOT net>
Cc:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>, djgpp AT delorie DOT com
Subject:	Re: Info Zip unzip-5.32 does not compile with DJGPP/gcc-2.8.0
Date:	Mon, 06 Apr 1998 14:46:45 +0200
References:	<Pine DOT SUN DOT 3 DOT 91 DOT 980405155545 DOT 5976Z-100000 AT is> <199804051604 DOT SAA21986 AT crimson DOT ihg DOT uni-duisburg DOT de> <3527E07E DOT 894A0D30 AT gmx DOT net>
In-Reply-To:	<3527E07E.894A0D30@gmx.net>
MIME-Version:	1.0

On Sun, 05 Apr 1998 19:50:22 +0000, Robert Hoehne wrote:

> If you haven't modified your djgpp.env file, especially not
> removed the LIBRARY_PATH setting in the [gcc] this can't be.
> 
> But if you have done so, probably because of the description
> from the README.DJGPP which coes with gcc280b.zip then this can
> happen because of a bug in that README :-(
> 
> I mentioned there, that you can safely remove the path settings
> in [gcc] and [cpp] but I forgot that the specs file is needed also
> to be find in one of the library paths. So either you move the specs
> file to %DJDIR%/lib/gcc-lib/djgpp/2.80 or you define the LIBRARY_PATH
> variable in the [gcc] section of DJGPP.ENV to contain at least the
> %DJDIR%/lib path.

Ah, yes, this is it. I removed the %DJDIR%/lib directory from
LIBRARY_PATH and added the `-remap´ entry to the specs file as you
suggested in the readme.djgpp file. Obviously I have nearly slept when
doing so. Editing the specs file and then seeing `gcc -v´ saying "Using
built-in specs" should trigger a humanware breakpoint, I guess ;-)
 
Regards...
		Michael

- Raw text -