-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
[adding bug-gnulib]
According to Longuet JeanCharles on 5/19/2008 11:44 AM:
|
|
| PS: Not sure this is related, but I did this test with the last version
(1.4.11) of m4, and a "make test" failed with :
| FAIL: test-fseeko.sh
| test-ftello.c:92: assertion failed
| ./test-ftello.sh: line 3: 22529 Aborted
./test-ftello${EXEEXT} 1 <"$srcdir/test-ftello.sh"
| FAIL: test-ftello.sh
|
| Host info :
| Linux 2.4.18
| glibc 2.2.5
| gcc 2.95.3
There is a possibility that this might have been fixed in the meantime (at
any rate, the ftello test is certainly more robust as a result of the m4
1.4.11 release and followon reports). Would you be interested in trying
the latest snapshot?
http://home.comcast.net/~ericblake/m4-1.5.89a.22-3498.tar.gz [1.25M]
http://home.comcast.net/~ericblake/m4-1.5.89a.22-3498.tar.gz.asc
http://home.comcast.net/~ericblake/m4-1.5.89a.22-3498.tar.bz2 [991k]
http://home.comcast.net/~ericblake/m4-1.5.89a.22-3498.tar.bz2.asc
http://home.comcast.net/~ericblake/m4-1.5.89a.22-3498.tar.lzma [751k]
http://home.comcast.net/~ericblake/m4-1.5.89a.22-3498.tar.lzma.asc
But even if it has not been fixed, your glibc is somewhat old (and newer
glibc appears to have been fixed). The bug only affects ftell after
ungetc of random bytes, so while it designates a bug in your libc, it is
not triggered by m4. You can run 'make -k check' to run the m4-specific
tests to prove this point.
- --
Don't work too hard, make some time for fun as well!
Eric Blake [EMAIL PROTECTED]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkgyxkgACgkQ84KuGfSFAYBKIACfWLsDTjJ2FTsl2BnJ+j+xsbt3
B1UAoLoepP9Gc5PZdPyzLzT8zJ7Ytf7O
=6bGT
-----END PGP SIGNATURE-----
