Date: Sun, 5 Apr 1998 16:00:24 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: Michael Mauch <michael DOT mauch AT gmx DOT de>
cc: djgpp AT delorie DOT com, Robert Hoehne <robert DOT hoehne AT gmx DOT net>
Subject: Re: Info Zip unzip-5.32 does not compile with DJGPP/gcc-2.8.0
In-Reply-To: <6g745h$bi2$2@news-hrz.uni-duisburg.de>
Message-ID: <Pine.SUN.3.91.980405155545.5976Z-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Content-Transfer-Encoding: 8bit
Precedence: bulk


On Sun, 5 Apr 1998, Michael Mauch wrote:

> gcc2.8.0 doesn't define __DJGPP_MINOR_ anymore.

How can that be?  Does gcc 2.8.0 bypass the %DJDIR%/lib/specs file?

Robert, can you explain that?  IMHO, a lot of programs will break if 
__DJGPP_MINOR__ is not defined.

> Can we put a specs file somewhere
> and define that value there? I seem to remember that gcc2.8.0 has a
> built-in specs file, but I don't know how to create a completely new
> one.

How about copying the DJGPP-standard specs file into the directory where 
2.8.0 expects it to be?

> Or shouldn't we count on having __DJGPP_MINOR__ defined? After all it's
> just used to print the DJGPP/gcc version number for `unzip -vī, not for
> any "real" functions (at least not in unzip).

__DJGPP_MINOR__ *must* be defined.  Several packages besides UnZip use it
to know which libc features can be relied upon, and will produce broken
programs if that symbol is undefined.  Emacs and TeX DVI drivers are some
particular examples of such packages.