From: cgf AT cygnus DOT com (Christopher Faylor)
Subject: Re: Problems with 980916 winsup under Windows 98
18 Sep 1998 11:36:09 -0700
Message-ID: <19980918140027.D23538.cygnus.cygwin32.developers@cygnus.com>
References: <3 DOT 0 DOT 5 DOT 32 DOT 19980914182707 DOT 008077c0 AT mail DOT mel DOT cybec DOT com DOT au>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
To: Trevor Yann <TYann AT vet DOT com DOT au>
Cc: cygwin32-developers AT cygnus DOT com

On Fri, Sep 18, 1998 at 07:21:42PM +1000, Trevor Yann wrote:
>The problem appears to be fixed under 98 as well. :-)
>
>I checked the hanging problem and it is still there. This seems to be worse
>than the last problem with the pc hanging, because sometimes the pc stays
>hung, and I have to do a hard reboot. Other times I get a blue screen.

AFAIK, this is the same as Win95.  It's too bad that Win98 doesn't fix
this problem.  I'd maintain that a program which uses the standard Win32 API
shouldn't be able to do this.

Of course, I could "maintain" that as loud as I want but it still wouldn't
make a difference.

It's possible that some forthcoming fixes to the sources will minimize this
but they won't be in time for B20, unfortunately.

>BTW I still had problems with the makefile.
>
>The line
>LIBGCC:=${subst \\,/,${shell $(CC_FOR_TARGET) -print-libgcc-file-name}}
>had to be replaced with
>LIBGCC:=${subst \,/,${shell $(CC_FOR_TARGET) -print-libgcc-file-name}}
>
>to get a successful make. It appears that gnu make doesn't need to escape
>characters here.

That doesn't seem very consistent, but whaddareya gonna do?
I've made the change to the sources.
-- 
cgf AT cygnus DOT com
http://www.cygnus.com/