delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/1997/05/19/13:35:54

From: noer AT cygnus DOT com (Geoffrey Noer)
Subject: Re: what went wrong?
19 May 1997 13:35:54 -0700 :
Approved: cygnus DOT gnu-win32 AT cygnus DOT com
Distribution: cygnus
Message-ID: <199705191749.KAA28822.cygnus.gnu-win32@cirdan.cygnus.com>
Original-To: stephenc AT wf DOT net (Stephen Crowley)
Original-Cc: gnu-win32 AT cygnus DOT com
In-Reply-To: <199705182114.QAA13995@odin.wf.net> from "Stephen Crowley" at May 18, 97 03:59:09 pm
X-Mailer: ELM [version 2.4 PL23]
Original-Sender: owner-gnu-win32 AT cygnus DOT com

Stephen Crowley wrote:
> 
> Just wondering but what did you guys do to screw up b18 so bad? The
> configure scripts that worked perfeclty with 17.1 wont work at all with
> b18, sometimes the script is supposed to wait for use input but it just
> keeps going and then it wont find files it creates in the /tmp dir, e.g. it
> creates a temp file to pass to gcc but gcc cant find the file, and also it
> goes into infinite recursion for some reason, keeps saying stack error or
> something.

I haven't seen problems like this when I've run configure scripts
using b18.  It is true that if you run out of stack space, gcc becomes
rather unhappy.  :-(

I also haven't seen a slowing in starting programs or in compiling
executables.  In fact, I see a speed-up in compile times over
beta 17...

-- 
Geoffrey Noer
noer AT cygnus DOT com
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request AT cygnus DOT com" with one line of text: "help".

- Raw text -


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