Re: m4-1.4.11: assert failure in two self tests on NetBSD

2008-04-11 Thread Eric Blake
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Thomas Klausner on 4/11/2008 12:07 AM: | Hi! | | m4-1.4.11 fails two selftests on NetBSD-4.99.48/amd64. Hi Thomas, and thanks for the report. Both of these failures are in the gnulib tests, hence I'm adding bug-gnulib. Could you please

Re: m4-1.4.11: assert failure in two self tests on NetBSD

2008-04-11 Thread Thomas Klausner
Hi Eric! Thanks for your reply. > Both of these failures are in the gnulib tests, hence I'm adding > bug-gnulib. Could you please also run 'make -k check' to see if the > M4-specific tests pass? Sure. Skipped checks were: ./109.changeword ./110.changeword ./111.changeword ./112.changeword .

Re: Working os/2 configuratie

2008-04-11 Thread Eric Blake
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Elbert Pol on 4/10/2008 2:49 PM: | Hi Eric, | | I attach the check.log it fails :( I guessed it might, since Bruno's patch for EMX was preliminary. At any rate, here's the relevant gnulib portions: Killed by SIGABRT pid=0x038a ppid=0x0

Re: m4-1.4.11: assert failure in two self tests on NetBSD

2008-04-11 Thread Eric Blake
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Thomas Klausner on 4/11/2008 6:29 AM: |> M4-specific tests pass? | | Sure. | Skipped checks were: | ./109.changeword ./110.changeword ./111.changeword ./112.changeword | ./113.changeword ./114.changeword | All checks successful | | Lo

Re: Working os/2 configuratie

2008-04-11 Thread Bruno Haible
Eric Blake wrote: > More failures without line numbers: > Killed by SIGFPE > FAIL: test-frexp.exe > Killed by SIGFPE > FAIL: test-frexpl.exe > Killed by SIGFPE > FAIL: test-printf-frexp.exe > Killed by SIGFPE > FAIL: test-printf-frexpl.exe > Killed by SIGFPE > FAIL: test-signbit.exe > > ... Bruno'

Re: Working os/2 configuratie

2008-04-11 Thread Eric Blake
Eric Blake byu.net> writes: Fixes for some (but not all) of Elbert's m4-specific test failures. > -esyscmd: [EMAIL PROTECTED] > +esyscmd: [\0] > > OK, a testsuite bug - I assumed that 'printf "[\0]"' is portable, but on > your platform, it prints literal \0 rather than the correct NUL byte. Bu