My apologies if I've misinterpreted which mailing list is appropriate,
or missed discussions in the archives (I could only find one mention
of thread support under Irix 6, and it didn't quite fit with my
reading of the situation).
Currently (0.9.5a) configuration using ./config on any Irix 6.*
release will be "nothreads". It is my belief that Irix implements
posix threads in all 6.5.* (and as far as I can tell 6.3) releases.
The documentation provided for the Irix pthreads implementation
indicates that the appropriate #define to ensure that safe behaviours
(eg a thread-safe errno) are switched on is -D_POSIX_C_SOURCE=199506L
I've configured with
./Configure threads -D_POSIX_C_SOURCE=199506L irix-mips3-gcc
but this, unfortunately, triggers one small problem, namely that one side
effect of this #define is to switch off BSD compatibility, so that
<sys/types.h> no longer #includes <sys/bsd_types.h>, and thus doesn't
get the content of <sys/select.h> causing the compilation of apps/s_server.c
to fall over as fd_set isn't typedef-ed any more. So, alternatively,
./Configure threads -D_POSIX_C_SOURCE=199506L -D_BSD_TYPES irix-mips3-gcc
which seems to work fine (configures, makes, and tests). The only
slight downside to this is that it will also clutter the namespace with
the following typedefs: physadr,unchar,u_char,ushort,u_short,uint,u_int,ulong,
u_long,quad. The alternative is to hack the sources (e_os.h?) to
explicitly #include <sys/select.h> on sgi's ...
I think therefore, unless I'm missing something obvious, that it ought
to be ok to replace the
::(unknown)::
in the {irix-mips3,irix64-mips4}-{gcc,cc} lines with
::-D_POSIX_C_SOURCE=199506L -D_BSD_TYPES::
and then arrange in ./config that Irix 6.(<3) releases get a different
configuration that doesn't try to do threading ...
-patrick (probably missing something obvious ...)
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
