Re: [Bug-wget] GNU wget 1.15 released

[Ray Satiro]

On 1/22/2014 2:09 PM, Gisle Vanem wrote:
> Okay. I'm having an issue with ioctl() in mswindows.c. It's really 
> rpl_ioctl()
> from gnulib:
>
> .text          0x004607a8       0x3c 
> g:/MingW32/src/gnu/gnulib/lib/libgnulib.a(ioctl.o)
>                0x004607a8                rpl_ioctl
>
> Almost on any url, wget aborts with this message:
>
> wget -d http://bla-bla
>
> DEBUG output created by Wget 1.15 (MingW) on Windows_NT.
> ...
> ---request end---
> ioctl() failed.  The socket could not be set as blocking.
> Winsock error: 0
>
> This application has requested the Runtime to terminate it in an 
> unusual way.
> Please contact the application's support team for more information.
>
> -------------
I'm pretty sure I wrote that code. I would not edit it out, if you are 
seeing it there is likely a problem with your build.

I just built wget v1.15 using MinGW with gcc 4.7.0 on Windows 7 SP1 x64 
and I don't see that. Both HTTP and HTTPS seem to be ok. I tried on 
Windows XP SP3 x86 and Windows 8 x64 as well and it looks ok. I haven't 
tested large file support (or anything, really).

You say *almost* any URL? Can you give an example? What happens if you 
try to get google's page:
wget http://www.google.com
wget --ca-certificate=c:\wget\root\bin\cacert.pem 
https://encrypted.google.com

> There should be no error; see "Winsock error: 0". I've just commented 
> out the
> if-statement with the abort() and things just work fine AFAICS.
>
> This is is on Win-XP SP3, wget built with MingW+gcc 4.7.2.
Well, there probably should be an error. The error you are seeing has 
come up before because when gnulib is built there could be some 
erroneous mixing of select and ioctl; one is native and the other is a 
gnu wrapper or something like that. Really they both should be gnulib 
wrappers, I think. I'd have to research my posts to wget and gnulib 
mailing lists to be sure. Here's one
http://comments.gmane.org/gmane.comp.web.wget.general/10697

Also there are some problems with later versions of MinGW, but I'm not 
sure about your version or if this is related:
http://mingw.5.n7.nabble.com/The-procedure-entry-point-ftelli64-could-not-be-located-in-the-dynamic-link-library-msvcrt-dll-td32856.html
That isn't a Wget bug really, it's just the direction they're heading 
with MinGW (which I disagree with because it seems like they're going to 
break backwards compatibility).

For reference here's my Windows build of wget-v1.15 (openssl) with MinGW 
instructions
http://sourceforge.net/projects/getgnuwin32/files/getgnuwin32/test%20builds/wget-1.15-release.f694b2e__mingw__2014-01-22.zip/download
509724732b5469b497a61f637b8a7d0fb1ac5c26 
*wget-1.15-release.f694b2e__mingw__2014-01-22.zip

My apologies if the mail came out formatted weird I'm using a different 
client.

Jay