bug-gnulib
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: test-fseek fails on W32


From: LRN
Subject: Re: test-fseek fails on W32
Date: Thu, 04 Apr 2013 00:21:02 +0400
User-agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:22.0) Gecko/20100101 Thunderbird/22.0a1

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 04.04.2013 00:00, Eric Blake wrote:
> On 04/01/2013 04:48 PM, Eric Blake wrote:
>> On 04/01/2013 04:36 PM, LRN wrote:
>>>>> 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"
>> 
>> Well, apparently the m4 files don't think they need to replace
>> fseek...
>> 
>>> S["HAVE_FSEEKO"]="1" S["HAVE_DECL_FSEEKO"]="1" 
>>> S["GNULIB_FSEEKO"]="1" S["GNULIB_FSEEK"]="1"
>> 
>> ...even though the gnulib modules are in use...
>> 
>>> 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"
>> 
>> ...and even though we know seek is broken on the platform.  Looks
>> like I'll have to figure out what went wrong; I'll probably have
>> a patch in the next 24 hours or so.
> 
> I'm still stumped on how to reproduce this; on latest gnulib.git 
> installed in a Cygwin setup, I did:
> 
> ./gnulib-tool --create-testdir --dir=testdir0 fseeko
> 
> then in that directory did a configure with a cross compiler:
> 
> ./configure --host=i686-pc-mingw32 --build=i686-pc-cygwin
> 
> and the resulting build passed all tests.  Looking in
> config.status, I see:
> 
> S["REPLACE_FSEEKO"]="0" S["REPLACE_FSEEK"]="1" 
> S["HAVE_FSEEKO"]="0" S["HAVE_DECL_FSEEKO"]="0"
> 
> which differs from your setup.  Maybe I should repeat my tests
> with mingw64 instead of the older mingw32?
> 
H-m-m-m...if the problem is in the way gnulib detects whether it needs
to replace fseek or not, then using mingw-w64 might give you different
results, since mingw.org and mingw-w64 headers and crt differ
significantly.
I'll try doing the same thing you listed above on my msys+mingw-w64
installation. Any particular things in the output i should send back?

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (MingW32)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJRXI8qAAoJEOs4Jb6SI2CwwXQH/imkrd7aEvYz7YE7QYTDas93
20ky7qmAe2rq7Eeqg1FLtwS08qhF3K+F0w8aLunOm9Xcx5GTkORR/F6Wv//ClHne
0lZ6HwJw3OZzwkPxdiRxsOXyjhB8WI5uGmxsXZaIHsEYGIs0GmA7EpqHZmv6389J
WlppHea07XU7y2pnqg2ZzFr7/DhFp0poUafnNt5QBUP3mM1RhodgHbmjp9/jQhvq
7gYJUdSrK7SyZwKHhL1+q/GQy87c33K4vMjMOqyIAMiwNAf9iQidlV5mtmZl/s6Q
fLHn7D2Rb5t8Sw5cd84XxhL17gmLiBvtQ+7t6eEDTnYigYLcDbtAXANpKtnR3WU=
=y+rT
-----END PGP SIGNATURE-----



reply via email to

[Prev in Thread] Current Thread [Next in Thread]