back to using OPENSSL_SYS_ULTRASPARC.

so when removing one reference, if should be replaced with the
appropriate number of colons, or chaos will follow...

never worked anyway. Note this is not going to HEAD as we intend to
provide an alternative solution as soon as 0.9.7 is out.

Yes, this implies that corresponding targets in beta6 pass the test suite.

MIT Kerberos.

This patch was taken from the OpenBSD copy of OpenSSL 0.9.7 beta3 with patches

PR: 420

Submitted by: Jeffrey Altman <jaltman@columbia.edu>, "Kenneth R. Robinette" <support@securenetterm.com>

the conditional was set to add the library directory to PATH when the
platform is NOT Cygwin.  Corrected.
PR: 404

Confirmed by Mark Daniel <Mark.Daniel@wasd.vsm.com.au>

PR: 413

(I wonder why s2_connect() handles the initial buffer allocation slightly
differently...)
PR: 416

PR: 411

irix-mips. The bug was introduced with accelerated support for x86_64.
My fault! Fixed now.

Submitted by: "Kenneth R. Robinette" <support@securenetterm.com>
Reviewed by:
PR:

and then didn't support it very well.  And that when there already is a
useful variable for exactly this kind of thing; EX_LIBS...

has been performed (and possibly changed), have it depend on Makefile.ssl.

Incidently, it now compiles so much better without _POSIX_C_SOURCE.

defined in DECC$TYPES.H.  If _POSIX_C_SOURCE is defined, certain types do
not get defined (u_char, u_int, ...).  DECC.H gets included by assert.h
and others.  Now, in6.h uses the types u_char, u_int and so on, and gets
included as part of other header inclusions, and will of course fail because
of the missing types.

On the other hand, _XOPEN_SOURCE_EXTENDED is needed to get gethostname()
properly declared...

Solution: define _XOPEN_SOURCE_EXTENDED much later, so DECC$TYPES.H has
a chance to be included *first*, so the otherwise missing types get defined
properly.

Personal: *mumble* *mumble*

${prefix}/lib/pkgconfig, not ${prefix}/lib/pkginfo.

${prefix}/lib/pkgconfig, not ${prefix}/lib/pkginfo.

Linux for example doesn't exhibit this behaviour, but I add "exit 0" to all
potentially affected rules, just to be on the safe side.