Tom Titchener wrote:
>
> Open SSL Developers -
>
> 1) When I copy over or unzip from the cvs hierarchy, the
> protections on the crypto/x509v3/old_v3 directory files
> always prevent the copy. It's safe to ignore this.
> Nothing gets built in this directory anyway.
>
Yep that's just legacy stuff.
> 2) You need to create a date.h file by hand in the crypto
> directory. If you're running a real shell, you can type
> the line from the makefile.ssl, e.g.:
>
> $ cd crypto
> $ echo "#define DATE \"`date`\"" >date.h
>
Yep. I'll get the perl config script to do this automatically sometime.
> 3) The version of perl I'm running doesn't like this bit of
> syntax in the top-level configure source:
>
[example deleted]
>
> The version of perl I'm running is:
>
> $ perl -version
>
> This is perl, version 5.002 with DEBUGGING EMBED
>
My version is 5.004_02 and it has no problems with this.
>
> 5) Running configure converts the generic (.org) versions of files
> to local versions according to your configuration. However there's
> one that gets forgotten--pem.org. Fortunately, pem.org is the same
> as pem.h, so you just need to
>
> $ cd to crypto/pem
> $ cp pem.org pem.h
>
I'm not sure they are the same. They are almost the same except for a
few architecture specific #defines with the size of structures. You can
simulate what other Makes do by building the ctx_size program and doing
ctx_size < pem.org > pem.h
I think the simplest way to handle this is to hard code the right values
in the config script for those architectures that need it.
>
> 7) Next you wanna create your ntdll.mak file:
>
> $ perl util/mk1mf.pl dll VC-WIN32 > ms/ntdll.mak
>
> 8) And your two .def files (there are lots of new source modules):
>
> $ perl util/mkdef.pl 32 ssleay > ms/ssleay32.def
> $ perl util/mkdef.pl 32 libeay > ms/libeay32.def
>
The batch file ms\do_ms does this. It shouldn't really because not many
people have the assembler 'ml'.
If you don't have the assembler then:
perl util\mk1mf.pl no-asm dll VC-WIN32 > ms\ntdll.mak
will build the makefile without assembly language stuff.
> That's it, now you *should* be able to type
>
> $ nmake -f ms/ntdll.mak
>
There are still some legacy issues in the Windows stuff: the main
application is still called 'ssleay' and the DLL's have EAY in their
names.
Just a few additional comments. The Windows stuff may occasionally fall
behind the main stuff from time to time. Until recently attempting
to get this stuff to compile under Win32 at all was a non starter: I
spent an annoying amount of time fixing it up.
If it doesn't seem to compile right or misses files out then it may be
that the tarball doesn't have the latest Win32 stuff. In this case you
need to do a: "make files" at the top level to rebuild the MINFO file
(which is where the makefiles come from). You might have to do this from
Unix.
If the mkdef.pl stuff complains about missing functions and the compile
fails due to undefined symbols try adding the undefined functions to the
end of util/*.num files. Note: if you do this then there is no guarantee
that the numbers will match those when the main distribution is fixed,
in which case you will need to recompile anything linked against the
incompatible DLL.
Steve.
--
Dr Stephen N. Henson. UK based freelance Cryptographic Consultant.
For info see homepage at http://www.drh-consultancy.demon.co.uk/
Email: [EMAIL PROTECTED]
NOTE NEW (13/12/98) PGP key: via homepage.
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
