MinGW - Minimalist GNU for Windows

Earnie Boyd wrote:
> This will become part of the updated msysDTK and is currently
> located in the Snapshot->MSYS release.

Just curious: did you run this through its test suite?  How well
did it perform?

It might also be worth considering an upgrade of m4, to m4-1.4.5;
(bison is dependent on m4, and m4-1.4.5 is reported to include a
number of significant bug fixes, over the m4-1.4 we currently
provide).  I recently built this as a native app.  OOTB, it built
without a murmur, but then promptly failed every one of its test
cases.  However, with the attached minor patch, it passes all but
three of the 104 tests in the suite.

I don't really have time to pursue the three failures, at present;
I think I should submit a bug report to bug-m4@....

Regards,
Keith.

--- src/m4.c    2006/07/17 15:23:02     1.1
+++ src/m4.c    2006/07/18 11:38:57
@@ -279,6 +279,11 @@

   program_name = argv[0];

+  /* Prefer binary mode output for stdout/stderr
+   * on platforms which differentiate it from text. */
+  SET_BINARY (STDOUT_FILENO);
+  SET_BINARY (STDERR_FILENO);
+
   include_init ();
   debug_init ();
 #ifdef USE_STACKOVF
--- lib/binary-io.h     2006/07/17 15:23:39     1.1
+++ lib/binary-io.h     2006/07/17 15:24:58
@@ -37,12 +37,12 @@
 # undef O_TEXT
 #endif
 #if O_BINARY
-# if !(defined __EMX__ || defined __DJGPP__ || defined __CYGWIN__)
+# if !(defined __EMX__ || defined __DJGPP__ || defined __CYGWIN__ || 
defined __MINGW32__)
 #  define setmode _setmode
 #  undef fileno
 #  define fileno _fileno
 # endif
-# if defined __DJGPP__ || defined __CYGWIN__
+# if defined __DJGPP__ || defined __CYGWIN__ || defined __MINGW32__
 #  include <io.h> /* declares setmode() */
 # endif
 # ifdef __DJGPP__

Quoting Keith MARSHALL <keith.marshall@...>:

> Earnie Boyd wrote:
>> This will become part of the updated msysDTK and is currently
>> located in the Snapshot->MSYS release.
>
> Just curious: did you run this through its test suite?  How well
> did it perform?
>

ERROR: 145 tests were run,
2 failed unexpectedly.
13 tests were skipped.
## -------------------------- ##
## testsuite.log was created. ##
## -------------------------- ##

Please send `testsuite.log' and all information you think might help:

   To: <bug-bison@...>
   Subject: [GNU Bison 2.3] testsuite: 31 33 failed




Earnie Boyd

http://shop.siebunlimited.com

Earnie Boyd wrote, quoting me:
>> Just curious: did you run this through its test suite?  How well
>> did it perform?
>
> ERROR: 145 tests were run,
> 2 failed unexpectedly.
> 13 tests were skipped.

So significantly better than the ~50% failure I saw with a native
build, then.  Did it need much patching?

> ## -------------------------- ##
> ## testsuite.log was created. ##
> ## -------------------------- ##
>
> Please send `testsuite.log' and all information you think might help:
>
>   To: <bug-bison@...>
>   Subject: [GNU Bison 2.3] testsuite: 31 33 failed

It might be worth submitting that as a bug report; I've found Paul
Eggert to be quite receptive, and I believe he is associated with
the bison project.

Just out of interest, here's what I saw, just now, when I ran the
bison-2.3 test suite on my Ubuntu 6.06 laptop:

## ------------- ##
## Test results. ##
## ------------- ##

156 tests were successful.
2 tests were skipped.

Regards,
Keith.

Quoting Keith MARSHALL <keith.marshall@...>:

> Earnie Boyd wrote, quoting me:
>>> Just curious: did you run this through its test suite?  How well
>>> did it perform?
>>
>> ERROR: 145 tests were run,
>> 2 failed unexpectedly.
>> 13 tests were skipped.
>
> So significantly better than the ~50% failure I saw with a native
> build, then.  Did it need much patching?
>

I used the Cygwin source; the patching was to match __MSYS__ to __CYGWIN__.

>> ## -------------------------- ##
>> ## testsuite.log was created. ##
>> ## -------------------------- ##
>>
>> Please send `testsuite.log' and all information you think might help:
>>
>>   To: <bug-bison@...>
>>   Subject: [GNU Bison 2.3] testsuite: 31 33 failed
>
> It might be worth submitting that as a bug report; I've found Paul
> Eggert to be quite receptive, and I believe he is associated with
> the bison project.
>

I'm quickly running out of time again; I've been moved to another team 
at my real job to help with putting out fires in a process that 
contains about 20 applications.  I'm in training now.  Once I have some 
spare moments I would like to find the cause of the errors with MSYS 
itself.

Earnie Boyd

http://shop.siebunlimited.com

Earnie Boyd wrote, quoting me:
>>> Please send `testsuite.log' and all information you think might help:
>>>
>>>   To: <bug-bison@...>
>>>   Subject: [GNU Bison 2.3] testsuite: 31 33 failed
>>
>> It might be worth submitting that as a bug report; I've found Paul
>> Eggert to be quite receptive, and I believe he is associated with
>> the bison project.
>
> I'm quickly running out of time again;

It may be sufficient to just create a new mail, copy and paste
that subject line, and attach the testsuite.log you already have;
surely you can spare the few seconds that would take?

> I used the Cygwin source; the patching was to match __MSYS__ to
> __CYGWIN__.

OTOH, if the Cygwin source differs significantly from the native
GNU package, then you may need to provide a bit of supplementary
explanation; I appreciate that that may be an excessive burden.

Regards,
Keith.