On Fri, Apr 3, 2009 at 17:17, Daniel Stenberg <daniel_at_haxx.se> wrote:

> Yes. We're gambling here that most people on systems that feature 64bit file
> operations will want to have those features enabled. That's basically what
> the "potential" part is about in the "potential risk" claim.
>
> But for systems that are capable of running configure, such as I would
> assume most systems that can use the Sun Compiler, configure will determine
> the type and do the necessary typedef and put that in a public header file
> to be used by applications. That typedef _does not_ include that super-huge
> #ifdef thing. At least it shouldn't in most circumstances.

You are assuming that systems running the Sun Compiler will only
deliver one set of libraries: either 32-bit or 64-bit.

This is not the case at all with Solaris proper: we always deliver
both 32-bit and 64-bit libraries. However, we can only deliver one set
of header files, and the same set of header files must work across all
ISA's and bitness sizes.

This is why the whole discussion was about the default non-generated
curlbuild.h header files, and not the ./configure generated header
file, which cannot be commonly used across 32-bit and 64-bit
libraries.

--Stefan

-- 
Stefan Teleman
KDE e.V.
stefan.teleman_at_gmail.com