Bruno Haible <br...@clisp.org> writes: >> Starting test_cond .../bin/sh: line 5: 3124 Aborted (core >> dumped) >> FAIL: test-cond.exe >> >> Starting test_lock .../bin/sh: line 5: 1336 Aborted (core >> dumped) >> FAIL: test-lock.exe >> >> Starting test_tls .../bin/sh: line 5: 3444 Aborted (core >> dumped) >> FAIL: test-tls.exe > > The pthread implementation is apparently broken on Cygwin, see > <http://cygwin.com/ml/cygwin/2009-08/msg00283.html>. I have added some > code to m4/threadlib.m4 that disables threads on Cygwin 1.5.x by default. > So, for me, the results are: > > SKIP: test-cond.exe > > Skipping test: multithreading not enabled > SKIP: test-lock.exe > > Skipping test: multithreading not enabled > SKIP: test-tls.exe > > [Oops, 'test-cond' should display the reason why the test is being skipped.] > > What's the result of "uname -r" on your machine?
I still get failures here, for Cygwin 1.7.x: Starting test_cond .../bin/sh: line 5: 3504 Aborted (core dumped) FAIL: test-cond.exe ... Starting test_lock .../bin/sh: line 5: 3500 Aborted (core dumped) FAIL: test-lock.exe ... Starting test_tls .../bin/sh: line 5: 2560 Aborted (core dumped) FAIL: test-tls.exe See http://autobuild.josefsson.org/gnulib/log-201002171652277193000.txt Should m4/threadlib.m4 disable threads on cygwin 1.7.x too? There is a 1.[0-5].* regexp in there now. /Simon
