It doesn't seem the patches to support >2GB files works on
Windows. Wget hangs indefinitely at the end of transfer.
E.g.
\wget.exe ftp://ftp.ncbi.nih.gov/blast/db/FASTA/nt.gz
--05:38:54-- ftp://ftp.ncbi.nih.gov/blast/db/FASTA/nt.gz
=> `nt.gz'
Resolving ftp.ncbi.nih.gov... 130.14.29.30
C
Gisle Vanem <[EMAIL PROTECTED]> writes:
> It doesn't seem the patches to support >2GB files works on
> Windows. Wget hangs indefinitely at the end of transfer.
Is there a way to trace what syscall Wget is stuck at? Under Cygwin I
can try to use strace, but I'm not sure if I'll be able to repeat
"Hrvoje Niksic" wrote:
Gisle Vanem <[EMAIL PROTECTED]> writes:
It doesn't seem the patches to support >2GB files works on
Windows. Wget hangs indefinitely at the end of transfer.
Is there a way to trace what syscall Wget is stuck at? Under Cygwin I
can try to use strace, but I'm not sure if I'll b
Steve Thompson <[EMAIL PROTECTED]> writes:
> I have found in another context that the Windows C run-time library
> can't handle files larger than 2GB in any context, when using fopen,
> etc. The size of off_t is 4 bytes on IA32.
I know that, but stdio is not necessarily tied to off_t anyway --
ex
Gisle Vanem <[EMAIL PROTECTED]> writes:
> There is strace for Win-NT too. But I dare not install it to find
> out.
Hmm, OK.
> PS. it is quite annoying to get 2 copies of every message.
I'll try to remember to edit the headers to leave your private address
out.
> Also, there should be a "Reply-
