Good morning,
I know that the older 16 bit support is not being kept up to date, but I'm
hoping there is someone that has a suggestion how to fix this.
I am trying to build the library for an embedded DR-DOS target running on
386 and 486 processors on PC/104 cards.
The target system is
Ampro 386/25MHz or 486/133MHz CPUs
Boot Diskette image built in Flash ROM (R/O file system)
DR-DOS 5.0
NE2000 Ethernet card
Novell TCP/IP stack and socket library
(Taken from their LAN Workplace SDK)
The development platform is
NT 4 SP5
ActiveState Perl build 515
VC++ 1.50c
MASM 6.00B
The plan is to be able to establish an RC4 encrypted connection between this
target and a service running on an NT server. Both ends are running our own
applications. I want to open the socket, skip the certificate exchange, use
DH to exchange a session key and enable the encryption for all traffic until
the socket is closed. This is for a POS system that will initiate the
connection about 2:30 am, after running an End Of Day audit, and be online
until the next EOD. All private secrets will be kept in a local disk file.
The initial step was
Perl configure no-threads 386 VC-MSDOS
I then made some manual changes to the ms\msdos.mak file
INSTALLTOP=E:\COMMS\msdos\openssl.095
CC=cl
CFLAG=-O1 -DMSDOS -DNO_SOCK /G3 # -O1 optimizes for speed
SRC_D=E:\COMMS\msdos\openssl.095
When I actually try to make the library (nmake -f ms\msdos.mak) everything
appears to work until it gets to crypto/bio/bss_log.c, where I get the
following error:
cl -o tmp\bss_log.o -Ioutinc -Itmp -O1 -DMSDOS -DNO_SOCK /G3 -c
E:\COM
MS\msdos\openssl.095\crypto\bio\bss_log.c
Microsoft (R) C/C++ Optimizing Compiler Version 8.00c
Copyright (c) Microsoft Corp 1984-1993. All rights reserved.
e:\comms\msdos\openssl.095\crypto\bio\bss_log.c
e:\comms\msdos\openssl.095\crypto\bio\bss_log.c(73) : fatal error C1083:
Cannot
open include file: 'syslog.h': No such file or directory
NMAKE : fatal error U1077: 'C:\WINNT\system32\cmd.exe' : return code '0x2'
Stop.
Looking at the source, it's obvious that it's not expecting to have MSDOS
defined, the #IFDEF's only check for WIN32 and __ultrix.
Is there a quick and easy way to remove or screen out this log function and
anything that can't work in the MSDOS world? Is there any way?
Thank you,
Bob McConnell
Principal Communications Programmer
The CBORD Group, Inc.
61 Brown Road
Ithaca, NY 14850-1247
Phone 607 257-2410
Fax 607 257-1902
email [EMAIL PROTECTED]
web www.cbord.com
______________________________________________________________________
OpenSSL Project http://www.openssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
