Change submitted by Doug Kaufman. He writes:

I just compiled the 9.9-dev version from the 12022007 tarball under
  DJGPP. There were only 2 changes needed, one for b_sock.c, since
  DJGPP with WATT32 doesn't define socklen_t and one for testtsa to
  handle DOS style path separators. I also noted what seems to be a
  typographical error in ts.pod. The test suite passes. The patch is
  attached.

  Since I am in the US, I have sent notifications to the Bureau of
  Industry and Security and to the NSA.
This commit is contained in:
Richard Levitte
2007-12-03 09:02:29 +00:00
parent 544b82e493
commit 28f7e60d47
3 changed files with 7 additions and 3 deletions

View File

@@ -800,7 +800,7 @@ int BIO_accept(int sock, char **addr)
if (addr == NULL) goto end; if (addr == NULL) goto end;
#ifdef EAI_FAMILY #ifdef EAI_FAMILY
# if defined(OPENSSL_SYS_VMS) || defined(OPENSSL_SYS_BEOS_BONE) # if defined(OPENSSL_SYS_VMS) || defined(OPENSSL_SYS_BEOS_BONE) || defined(OPENSSL_SYS_MSDOS)
# define SOCKLEN_T size_t # define SOCKLEN_T size_t
# else # else
# define SOCKLEN_T socklen_t # define SOCKLEN_T socklen_t

View File

@@ -370,7 +370,7 @@ See L<ca(1)|ca(1)> for description. (Optional)
The name of the file containing the hexadecimal serial number of the The name of the file containing the hexadecimal serial number of the
last time stamp response created. This number is incremented by 1 for last time stamp response created. This number is incremented by 1 for
each response. If the file does not exit at the time of response each response. If the file does not exist at the time of response
generation a new file is created with serial number 1. (Mandatory) generation a new file is created with serial number 1. (Mandatory)
=item B<crypto_device> =item B<crypto_device>

View File

@@ -5,7 +5,11 @@
# #
SH="/bin/sh" SH="/bin/sh"
PATH=../../apps:$PATH if test "$OSTYPE" = msdosdjgpp; then
PATH="../apps\;$PATH"
else
PATH="../apps:$PATH"
fi
export SH PATH export SH PATH
OPENSSL_CONF="../CAtsa.cnf" OPENSSL_CONF="../CAtsa.cnf"