-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 02.04.2013 02:33, Eric Blake wrote: > On 04/01/2013 04:25 PM, LRN wrote: >>> That should be fixed, since a seek succeeding on a pipe is >>> contrary to POSIX. Is fseek being replaced on W32? >> The package that hosts the instance of gnulib on which the >> failure was observed is GnuTLS-3.1.5. I'm not sure whether it >> replaces fseek or not, i don't see anything like that in its >> configure.ac, and there is no special configure for its gl >> subdirectory. However, that subdirectory does have fseek.c and >> fseeko.c, and m4 subsubdirectory has fseek.m4. But fseeko.o or >> fseek.o are not produced when the packages is compiled. >> >>> If so, the gnulib replacement has a bug - it should be >>> preventing fseek() from succeeding on a pipe. >> Apparently, the MSVCRT implementation of fseek() is used. >> >>> If not, then we should fix the m4 tests to filter out the >>> buggy W32 fseek and install the gnulib replacement. >> >> I'm unsure of how they work. > > What does 'grep _FSEEK config.status' show? $ grep _FSEEK config.status S["REPLACE_FSEEKO"]="0" S["REPLACE_FSEEK"]="0" S["HAVE_FSEEKO"]="1" S["HAVE_DECL_FSEEKO"]="1" S["GNULIB_FSEEKO"]="1" S["GNULIB_FSEEK"]="1" D["HAVE_FSEEKO"]=" 1" D["HAVE_DECL_FSEEKO"]=" 1" D["GNULIB_TEST_FSEEK"]=" 1" D["GNULIB_TEST_FSEEKO"]=" 1" D["HAVE_RAW_DECL_FSEEKO"]=" 1"
> How about 'grep LSEEK_PIPE config.h'? $ grep LSEEK_PIPE config.status D["LSEEK_PIPE_BROKEN"]=" 1" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (MingW32) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJRWgvsAAoJEOs4Jb6SI2Cw4ZIIANhZfOpEVnq5V3nQWQj1i5aU vR/wgwa4GKnNyYhB+fDs1aypE4/NgWi1yW/Scr3GpMTJgmVdwzXN5WEh7TUFyyXP WZSU0X6Z/Poh36+JPESmSYm55c4PvDswVfpqAs7xmqgH8FlrjYVNMKm7TDc0q+Jd T4fUAKxowbNiNujrbn7uh1CW17rsf7ytHf4oe3higQyLrwRwE8DWzaLTLMtAAt0r uqqCevUrFNAWHrpo3qcA3WEOYGBsFhCVh0LaVt4dEOit2UaqrHI72WURn7+rwiHN mqmd/eGJzEof48cfxr3R10eeYG6cmuzxM8x1BdqCxdE16LtU25JuZjRb0GdmyVk= =P+BX -----END PGP SIGNATURE-----
