2011/10/31 Vincent Torri <vincent.torri_at_gmail.com>:

> in src/main.c :
> #if defined(WIN32) && !defined(__MINGW64__)

You better grab a newer snapshot no src/main.c since 2011 october 4.

> According to the mingw-w64 dev, to detect any mingw-w64 compilers, one
> should use __MINGW64_VERSION_MAJOR instead of __MINGW64__.
>
> See : http://sourceforge.net/mailarchive/message.php?msg_id=28305973

Not so, according to
http://www.mail-archive.com/mingw-w64-public@lists.sourceforge.net/msg00638.html

If there's no other option than using a compiler specific macro, we
better use a predefined macro that does not require inclusion of any
header in order to 'see' it.

Those two projects have created a horrible situation relative to the
ambiguity of their names and preprocessor macros which only hurts them
both, and any derivative of them.

Could you try a recent libcurl snapshot and report back actual
situation mentioning clearly which project's compiler is used, as well
as availability of a function named exactly 'ftruncate' wich takes a
64bit variable as second argument?

Notice that Günter has several whatever64mingw autobuilds that run all
days and show no problem in that area.

-- 
-=[Yang]=-
-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-library
Etiquette:  http://curl.haxx.se/mail/etiquette.html