Hash: SHA256

Hrvoje Niksic wrote:
> Micah Cowan <[EMAIL PROTECTED]> writes:
>>> Or getting the definition requires defining a magic preprocessor
>>> symbol such as _XOPEN_SOURCE.  The man page I found claims that the
>>> function is defined by XPG4 and links to standards(5), which
>>> explicitly documents _XOPEN_SOURCE.
>> Right. But we set that unconditionally in <sysdep.h>,
> Only if you made it so.  The config-post.h code only set it on systems
> where that's known to be safe, currently Linux and Solaris.  (The
> reason was that some systems, possibly even Tru64, failed to compile
> with _XOPEN_SOURCE set.)

You're right, of course. It's not unconditional.

I can't even begin to fathom why some system would fail to compile in
such an event: _XOPEN_SOURCE is a feature request, not a guarantee that
you'll get some level of POSIX. Do you happen to remember the system?

I'd rather always define it, except for the systems where we know it
fails, rather than just define it where it's safe.

> Also note that Autoconf tests don't include sysdep.h, so the test
> could still be failing.  It would be worth investigating why curl's
> Autoconf test passes and ours (probably) doesn't.

I thought the Autoconf tests were testing merely for the function's
linkability... but yeah, maybe adding setjmp.h to the checked headers
will mean it's included for the function tests, or something. I'll play

- --
Micah J. Cowan
Programmer, musician, typesetting enthusiast, gamer...

Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org


Reply via email to