Hey

As we've seen before, there are times when "people" manage to build their
libcurl-using applications without enabling 64bit sizes and thus the
application and libcurl end up have different ideas about how the *_LARGE
options work and what size the curl_off_t type is.

One example can be found in this Debian bug report:

         http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=481975

Maybe it is time to go back and see if we can generate a fine header based on
the configure results so that apps will do less bad?

-- 
  / daniel.haxx.se