[Top][All Lists]

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

[Bug-wget] Run-time issues with Wget2 1.99.1 built with MinGW

From: Eli Zaretskii
Subject: [Bug-wget] Run-time issues with Wget2 1.99.1 built with MinGW
Date: Sat, 12 May 2018 11:50:44 +0300

> From: Tim Rühsen <address@hidden>
> Date: Tue, 1 May 2018 15:15:26 +0200
> GNU Wget2 is the successor of GNU Wget, a file and recursive website
> downloader.
> Designed and written from scratch it wraps around libwget, that provides
> the basic functions needed by a web client.
> Wget2 works multi-threaded and uses many features to allow fast operation.
> In many cases Wget2 downloads much faster than Wget1.x due to HTTP zlib
> compression, parallel connections and use of If-Modified-Since HTTP header.

Thanks.  I've built this using mingw.org's MinGW GCC and runtime
support, and found the following run-time issues:

 . The help screen shows the command name as "wget", not "wget2".  is
   that deliberate?

 . Error message is displayed at startup about False Start, due to
   using GnuTLS 3.4.  Why not simply silently avoid using the False
   Start option by default on such systems?

 . Progress bar displays escape sequences, which are not converted to
   colors on MS-Windows.  I see there are functions in
   libwget/console.c that produce colors on Windows: would you prefer
   using them for progress bar, or would you rather have
   Windows-specific code in bar.c?

 . The tests that use libmicrohttpd all fail, and all pop up the
   Windows UAC elevation dialogue.  I don't yet know why that happens,
   and I'm looking into this issue.  To help me out, could you perhaps
   describe how libmicrohttpd is involved in wget2 tests that use it?
   What is the main idea, and how should I interpret the test logs
   (which includes quite a bit of text that doesn't really explain


reply via email to

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