%% "J. Grant" <[EMAIL PROTECTED]> writes: jg> I am wondering why 12 additional tests are failing on MSVC build jg> now. The code I tested previously (beta2 with MinGW fixes) only jg> had 20 failures on MSVC build, and 24 failures on MinGW build if jg> my records are correct. This has leaped to 33 (MSVC) and 36 jg> (MinGW) in my tests.
jg> misc/general3 ........................................... FAILED (9/10 passed) This failure is almost certainly due to the change in backslash-newline handling, since misc/general3 is where I added all my testing. I'm sort of surprised you only got one failure here; there are a lot of different backslash-newline tests. jg> Tests which only fail because of incorrectly created base output file: jg> features/recursion jg> options/dash-I.mk jg> targets/DEFAULT jg> variables/CURDIR jg> variables/MAKE In what way were they incorrectly created? jg> These are the tests which I think we should try and find solutions for: jg> work/features/export.mk UNEXPORT_ALL=1 jg> features/export.mk EXPORT_ALL=1 UNEXPORT_ALL=1 jg> features/patspecific_vars.mk jg> functions/abspath jg> functions/value jg> functions/wildcard.mk print2 jg> functions/wildcard.mk clean jg> variables/special Don't know about these. jg> options/dash-l.mk -l 0.0001 -j 4 I don't think Windows supports the -l option so I doubt that this test should even be invoked. I've make some changes (checked in just tonight) that tries to handle environment variables more safely than previous versions, just in case some variables are leaking from test to test (I don't know if Windows allows that to happen). -- ------------------------------------------------------------------------------- Paul D. Smith <[EMAIL PROTECTED]> Find some GNU make tips at: http://www.gnu.org http://make.paulandlesley.org "Please remain calm...I may be mad, but I am a professional." --Mad Scientist _______________________________________________ Make-w32 mailing list [email protected] http://lists.gnu.org/mailman/listinfo/make-w32
