Re: [Quickfix-developers] [CVS] configure and _XOPEN_SOURCE

[Caleb E. <cal...@gm...>]

On Mon, 28 Feb 2005 14:24:42 -0600, Oren Miller <or...@qu...> wrote:

> Well, this used to be set to 1, but Bud Griffin reported that Solaris
> needs it to be 500:
> http://sourceforge.net/mailarchive/message.php?msg_id=10522888

It probably depends on the compiler and possibly operating system
release.  That message doesn't specify which compiler or Solaris
version he had trouble with.  We use SunPRO 5.3 on Solaris 2.8.  He
may be using gcc, or perhaps a less-buggy Sun C++ compiler.  CC -V
reports here:

CC: Sun WorkShop 6 update 2 C++ 5.3 Patch 111685-20 2004/03/19

The compiler can be detected by checking for the preprocessor macro
__SUNPRO_CC <= 0x530 if this helps.

Reading through the various system headers (<time.h> and
<sys/feature_tests.h>), setting _XOPEN_SOURCE=4 should be sufficient,
but this setting generates similar errors at compile time.

My best-guess solution for this would be to NOT define _XOPEN_SOURCE
if __SUNPRO_CC <= 0x530 as it doesn't seem to be required.  The
strptime prototype seems to be pulled in just fine without it.

This is also causing a cascading error effect.  Because compiler
errors are generated with _XOPEN_SOURCE defined, the configure test
for socklen_t ends up failing to compile.  So configure thinks it
needs to define the macro socklen_t -> int, which causes additional
errors.

-- 
Caleb Epstein
caleb dot epstein at gmail dot com