Python-2.3.4 on OSF1 V4.0?

[Fredrik Lundh]

Edmond Rusjan wrote:

> I don't understand if the '_E' in '_Esetsockopt' is significant and/or
> where it comes from, but that's one difference that strikes me.
>
> [V4.0]$ grep setsockopt Modules/socketmodule.c|wc
>     11      39     498
> [V4.0]$ grep _Esetsockopt Modules/socketmodule.c|wc
>      0       0       0

the OSF/1 C libraries support multiple Unix dialects through a variety of
compatibility macros.  I'm not 100% sure, but I think _E is used for things
that explicitly require some level of X/Open-compatibility.

try adding a

#define _XOPEN_SOURCE_EXTENDED

to your test program (before you include the socket stuff), and see if
it still works.

if that breaks your test program, adding a corresponding #undef to the
socket module's source code might help.

</F>