Date: Wed, 9 Dec 1998 12:33:25 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Alessandro Pisani <alextxm AT tin DOT it>
cc: djgpp AT delorie DOT com, Andris Pavenis <pavenis AT lanet DOT lv>
Subject: Re: DJGPP 2.02 and GCC 2.8.1 PROBLEM [urgent!] [SOLVED!]
In-Reply-To: <Version.32.19981208202949.00e1a2a0@box1.tin.it>
Message-ID: <Pine.SUN.3.91.981209123242.7705M-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp AT delorie DOT com


On Tue, 8 Dec 1998, Alessandro Pisani wrote:

> >If that doesn't help, set LFN=n in the environment and see what happens 
> >then.
> 
> WOA !!! THIS WORKS !!!!!!! TA-DAAA !!! 
> Keeping djgpp 2.02 djgpp.env and setting LFN=n *in the environment* gcc
> 2.8.1 works fine.

This is a severe bug, and it's probably triggered by something
specific to your system setup.  Please report the information I asked
for: the size and time stamp of gcc.exe you are using.  It is
impossible to debug this problem further without knowing exactly which
version of the binary you use, since otherwise there is no way to
deduce the locus of the bug from the crash traceback you posted.

> gxx.exe that was working fine was the djgpp 2.02 one (it works fine both
> with LFN=y and LFN=n)

Once again, I asked whether this is gxx.exe from djdev202.zip, or the
one from gcc281b.zip.  Please report the size and time stamp of
gxx.exe as well.

> *predefines:
> -Dunix -Di386 -DGO32 -DMSDOS -DDJGPP=2 -DDJGPP_MINOR=1
> 
> should I change it in -DDJGPP_MINOR=2 for DJGPP 2.02 ?

Yes, you should.  However, if you have specs in your lib subdirectory,
GCC will use that one, and it already sets DJGPP_MINOR to 2.

> Also, the file djgpp.djl in the same dir is longer than the djgpp.djl
> in the %djdir%\lib, that is the DJGPP 2.02 one. Should I substitute the
> GCC one with the DJGPP 2.02 one ?

You should be able to use either one.

> PS: I hope that a fix to the buggy LFN-gcc 2.8.1/djgpp 2.02 behaviour
>     will be soon available ;)

Only if you help us debug this problem.  It obviously never happened
to anybody else, although there are quite a few people who work with
beta releases of v2.02 and GCC 2.8.1 with LFN enabled for quite some
time.  We need your help to debug this.