With whom do I discuss these changes? I have added MSDOS switches to four
files, and everything compiles. But I also had to change some switches in
msdos.mak, and I don't understand what RANLIB is for, so I just commented
it out for now.
I grabbed unistd.h and stat.h from Bob Stout's SNIPPETS library (SNIP9707).
All stat.h does is "#include <sys\stat.h>" where Micros~1 hides it.
My next problem is translating the "ar r" commands to "LIB". Basically, it
requires something like:
O_CRYPTO= $(LIB_D)\lib$(CRYPTO)
for each %o in $(CRYPTOOBJ); do LIB $(O_CRYPTO).lib +%o, $(O_CRYPTO).lst\; ;
done
But I doubt that I have the syntax correct. The semicolon after
$(O_CRYPTO).lst
is necessary to tell LIB that the command line is complete, so don't ask for
any additional files (non-interactive form). If you don't want a listing
file,
everything between the comma and semi-colon can be skipped.
There were some 'L's missing from shift constants in lines 226, 227 and 228
of crypto\des\set_key.c, but they weren't causing any of my problems.
If I really understood all that I know about this stuff, this project might
actually be fun.
Thank you for listening.
Bob McConnell
> -----Original Message-----
> From: Ulf Möller [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, March 09, 2000 11:47 AM
> To: Bob McConnell
> Cc: '[EMAIL PROTECTED]'
> Subject: Re: Trouble building MSDOS version
>
>
> On Thu, Mar 09, 2000 at 10:02:10AM -0500, Bob McConnell wrote:
>
> > 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.
>
> You'll have to add the relevent #ifdefs for MSDOS, there's no way
> around that. This is simple for bss_log.c because DOS has no logging
> facilities, but it's possible that there will be problems at other
> places as well.
______________________________________________________________________
OpenSSL Project http://www.openssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
