Eric Blake <e...@byu.net> writes: > According to Simon Josefsson on 8/20/2009 7:27 AM: >> These self-tests appears to invoke the external command 'tr' which >> doesn't work well under Windows, or does it? > > GNU Coding Standards state that tr can be assumed to be available (and it > should be part of mingw). But you are right that on Windows it is not a > standard command unless you have installed it (as part of MSYS, cygwin, > etc...)
I'm cross-compiling on GNU/Linux to Windows, and running the self-test using Wine. Perhaps it will work if I install tr.exe? >> FWIW, there are other failures too: >> >> test-pipe.c:79: assertion failed >> test-pipe.sh: iteration 4 failed >> test-pipe.c:79: assertion failed >> test-pipe.sh: iteration 5 failed >> test-pipe.c:79: assertion failed >> test-pipe.sh: iteration 6 failed >> test-pipe.c:79: assertion failed >> test-pipe.sh: iteration 7 failed >> FAIL: test-pipe.sh > > Hmm; that worked for me when cross-compiling from cygwin to mingw, but > maybe when executed directly in Windows, there is something affecting how > stderr is passed to child processes. I'll have to see if I can reproduce > your test setup. I'm running using Wine. Reproducing it on a Debian-like machine should be relatively easy: gnulib-tool --create-testdir --with-tests --dir m pipe-filter-gi cd m ./configure --host=i586-mingw32msvc --build=`build-aux/config.guess` make check You need at least the mingw32, wine, and binfmt-support packages. Btw, what's the difference between pipe-filter-gi and pipe-filter-ii? Maybe the description field should clarify this? /Simon
