On Apr 26 20:02, Corinna Vinschen wrote:
> On Apr 26 10:41, Corinna Vinschen wrote:
> > On Apr 25 18:08, [EMAIL PROTECTED] wrote:
> > > So I understand why there are (multiples of) six failures each -- these
> > > relinked versions in the old test suite (and the occurances in the new
> > > test
On Apr 26 10:41, Corinna Vinschen wrote:
> On Apr 25 18:08, [EMAIL PROTECTED] wrote:
> > So I understand why there are (multiples of) six failures each -- these
> > relinked versions in the old test suite (and the occurances in the new test
> > suite) are expected to fail with either dll-not-foun
On Apr 25 18:08, [EMAIL PROTECTED] wrote:
> So I understand why there are (multiples of) six failures each -- these
> relinked versions in the old test suite (and the occurances in the new test
> suite) are expected to fail with either dll-not-found or missing-symbol
> errors. But Cygwin calls
iginal Message-
>From: Larry Hall [mailto:[EMAIL PROTECTED]
>Sent: Sunday, March 21, 2004 9:56 PM
>To: Benson Margulies; [EMAIL PROTECTED]
>Subject: Re: SetErrorMode
>
>
>At 12:52 PM 3/21/2004, you wrote:
>>I'm trying to run some builds under cygwin with SetErr
.
The most frequent offenders are Java programs, but I can't find any
evidence that the Sun JVM calls SetErrorMode.
-Original Message-
From: Larry Hall [mailto:[EMAIL PROTECTED]
Sent: Sunday, March 21, 2004 9:56 PM
To: Benson Margulies; [EMAIL PROTECTED]
Subject: Re: SetErrorMode
A
At 12:52 PM 3/21/2004, you wrote:
>I'm trying to run some builds under cygwin with SetErrorMode set to
>avoid Windows dialog boxes in the event of hard errors. I'm failing. I
>get dialog boxes. Is cygwin doing anything to call SetErrorMode and undo
>my efforts, or do I need to look elsewhere?
You
6 matches
Mail list logo
