Re: gnulib-related warnings while running testsuite of wget-1.18.109-4734

2017-02-07 Thread Antonio Diaz Diaz
Paul Eggert wrote: I assume you're using an older version of GCC. Newer GCCs should be OK, Yes, this machine has gcc-4.1.2 instaled. and it's not worth the trouble to pacify the older ones. I just reported this here because it is part of a larger report to bug-wget and the maintainer of w

Re: gnulib-related warnings while running testsuite of wget-1.18.109-4734

2017-02-07 Thread Paul Eggert
I assume you're using an older version of GCC. Newer GCCs should be OK, and it's not worth the trouble to pacify the older ones.

gnulib-related warnings while running testsuite of wget-1.18.109-4734

2017-02-07 Thread Antonio Diaz Diaz
Hello, While testing wget-1.18.109-4734 on a 32-bit GNU/Linux system with glibc-2.5 and gcc-4.1.2, I got these warnings from gnulib files: mktime.c: In function 'mktime_internal': mktime.c:355: warning: comparison is always f

RE: bug#25633: porting gzip to Visual Studio 2015 failed due to redesign of CRT

2017-02-07 Thread Kees Dekker
Hi Bruno, >Most of these troubles should go away if you use the 'compile' and 'ar-lib' >auxiliary scripts, as described in section 2 of >http://git.savannah.gnu.org/gitweb/?p=gperf.git;a=blob_plain;f=README.windows >These instructions were tested with GNU gperf and a couple of other GNU >packages

RE: bug#25633: porting gzip to Visual Studio 2015 failed due to redesign of CRT

2017-02-07 Thread Kees Dekker
>gnulib has been updated to work with this platform on 2016-12-13, see >http://git.savannah.gnu.org/gitweb/?p=gnulib.git;a=commit;h=5506db6b006274762bf5ea1d23feb7a9801529c8 >Eric Blake replied: >> If you can help port gnulib to the newer visual studio 2015, I'm sure >> patches are welcome. >> ...

RE: bug#25633: porting gzip to Visual Studio 2015 failed due to redesign of CRT

2017-02-07 Thread Kees Dekker
>Are the mentioned patches in the snapshot that was provided by Jim? >In any case, I will check today. Thanks for prompt replies. >If you like, I can share some additional changes I've made, e.g. Visual Studio >does not like -g flag, a WIN32 define that should be _WIN32 (a CL.exe built-in >macro

Re: bug#25633: porting gzip to Visual Studio 2015 failed due to redesign of CRT

2017-02-07 Thread Eric Blake
On 02/07/2017 08:13 AM, Kees Dekker wrote: > Based on what I found today: the changes at low-level stdio in the FILE > struct are now complable (I did not have yet a chance to let pass gzip our > own internal tests, will do so later today or tomorrow). > But still some things are incorrect: > >

Re: bug#25633: porting gzip to Visual Studio 2015 failed due to redesign of CRT

2017-02-07 Thread Bruno Haible
Hello Kees, > If you like, I can share some additional changes I've made, e.g. Visual Studio > does not like -g flag, a WIN32 define that should be _WIN32 (a CL.exe built-in > macro), a workaround for missing #include_next directive (which is not > supported by Visual Studio), a struct that is in