www.delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp-workers/1998/07/16/20:10:09

Sender: nate AT cartsys DOT com
Message-ID: <35AAD98B.389C5B42@cartsys.com>
Date: Mon, 13 Jul 1998 21:07:39 -0700
From: Nate Eldredge <nate AT cartsys DOT com>
MIME-Version: 1.0
To: Andris Pavenis <pavenis AT lanet DOT lv>
CC: "John M. Aldrich" <fighteer AT cs DOT com>, djgpp-workers AT delorie DOT com
Subject: Re: Compile gives Abort! error
References: <Pine DOT A32 DOT 3 DOT 91 DOT 980711121850 DOT 189054A-100000 AT ieva05 DOT lanet DOT lv>

Andris Pavenis wrote:

> TEMP and TMP is used by gcc if TMPDIR is not defined (It's normally
> defined in DJGPP.ENV unless explicitly removed from there (I don't remember
> in which is looked first). NOTE: I'm talking about gcc-2.8.1 and didn't look
> in sources of previous versions.
> 
> >
> > I wonder: why not?  Seems to me we could just set TMPDIR to TEMP in
> > DJGPP.ENV.  Since DOS users have to have TEMP set reasonably anyhow,
> > that would save trouble of this kind.
> >
> 
> That can be one of solutions when DJGPP is residing on R/O disk.
> I don't think it's good by default.
> 
> gcc ends so when tries to put temporary files on read only disk.
> I met this, when wrote my installation of DJGPP to CD and forgot
> to edit DJGPP.ENV before (I was hurrying). Such CD is nice if I
> have to go somewhere and compile some program as there is no need to
> install anything.

Then I think what we really need is for GCC to handle that more
gracefully.  A cursory glance through the FSF GCC sources didn't show
anyplace where it might abort if the file didn't open, but it still
might be there, or only in the DJGPP sources (which I don't have
handy).  This is where `abort' giving SIGABRT and a traceback would be
helpful...
-- 

Nate Eldredge
nate AT cartsys DOT com


- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019