Message-ID:	<B0000054584@stargate.astr.lu.lv>
From:	"Andris Pavenis" <pavenis AT lanet DOT lv>
To:	alextxm AT tin DOT it
Date:	Wed, 9 Dec 1998 21:44:47 +0200
MIME-Version:	1.0
Subject:	Re: DJGPP 2.02/GCC 2.8.1 PROBLEM [re: Eli and Dj]
CC:	djgpp AT delorie DOT com
References:	<Version DOT 32 DOT 19981209173710 DOT 00e1f9c0 AT box1 DOT tin DOT it>
In-reply-to:	<Pine.SUN.3.91.981209193818.11864E-100000@is>
X-mailer:	Pegasus Mail for Win32 (v3.01d)
Reply-To:	djgpp AT delorie DOT com

On 9 Dec 98, at 19:52, Eli Zaretskii wrote:

> 
> On Wed, 9 Dec 1998, Alessandro Pisani wrote:
> 
> > Directory di D:\djgpp\bin
> > GCC      EXE       119.296  29/04/98  21.27 gcc.exe
> > G__~1    EXE         2.048  29/04/98  21.29 g++.exe
> > GXX      EXE        70.144  02/12/98  20.33 gxx.exe
> 
> This is an old version of GCC.  The latest binaries should be dated
> 22 October 1998.  Please download the latest GCC distribution and see if 
> that solves the problem.
> 
> > Please also note that the same executables works fine both with LFN=y and
> > LFN=y with DJGPP 2.01.
> 
> Are you sure?  How exactly did you test this?
> 
> I cannot think of any way that v2.02 could break GCC.  My guess about LFN 
> was based on a hunch that you have used v2.01 with LFN disabled, since 
> djgpp.env from v2.01 disables it.  The only file, except djgpp.env, that 
> GCC reads and that comes with djdev202 is lib/specs, and you already 
> tried to rename it.  You also tried to rename djgpp.env.
> 
> So I don't understand how can the same binary (gcc.exe) under the same
> circumstances (LFN=y) sometimes crash and sometimes not, depending on 
> whether it's v2.01 or v2.02, when all files that can affect it were 
> tested one by one and proved to be not the reason.  Anybody?
> 
> Maybe if you explain how exactly did you switch from v2.01 to v2.02 and 
> back while testing this problem, somebody could come up with an idea?
> 
> > Eli: i think this problem/bug is not specific to my pc config...
> >      but if you think it is, i can specify my pc config both software
> >      and hardware (remeber i use Ms-Win98 4.10.1998 of 15th May 1998,
> >      italian version).
> 
> Right now, it is more important to understand what is the cause of the 
> crash.  Only then we could decide whether the version of your OS is 
> relevant.
> 

Question: are You setting directory for temporary files in environment
(set TMPDIR=...) for example to place temporary files on RAM disk?

That release You are using crashes in some conditions when backslashes
are being used in TMPDIR. Please don't use them. That is fixed in 
later updates so consider upgrading.

Example:  specifiying TMPDIR=E: or TMPDIR=E:\ causes that release
of gcc.exe to crash.

If it is so then it's still remains unclear why it crashes not on both 2.01
and 2.02.

Andris

- Raw text -