I am new to the mailing list so please forgive me if this request is
inappropriate.
I have followed the instructions from INSTALL.W32 as follows
Borland C++ builder 5
---------------------
* Configure for building with Borland Builder:
> perl Configure BC-32
* Create the appropriate makefile
> ms\do_nasm
* Build
> make -f ms\bcb.mak
Steps 1 and 2 complete successfully.
The make (step 3) completes to the point where it has built
out32\libeay32.lib and out32\ssleay32.lib successfully
The next step (building tmp32\md4test.obj) fails
ilink32 -ap -Tpe -x -Gn tmp32\md4test.obj \
c0x32.obj, \
out32\md4test.exe,, \
out32\ssleay32.lib \
ut32\libeay32.lib cw32mt.lib import32.lib
Turbo Incremental Link 5.00 Copyright (c) 1997, 2000 Borland
Error: Unresolved external '_sha1_block_data_order' \
referenced from D:\OPENSSL_1.0.1F\OUT32\LIBEAY32.LIB|sha1dgst
Error: Unresolved external '_md5_block_asm_data_order' \
referenced from D:\OPENSSL_1.0.1F\OUT32\LIBEAY32.LIB|md5_dgst
If I try to use the libraries for any of my applications I get the same
error, for example
#include <openssl/md5.h>
void main()
{
unsigned char md16[16];
MD5("Hello", 5, md16);
}
The linker fails with
Unresolved external '_md5_block_asm_data_order
This looks like a bug in the borland configuration
HASH_BLOCK_DATA_ORDER
ends up being #defined as
sha1_block_data_order
but because of various values set by configuration and do_nasm the
compilation of the sha1_block_data_order function never happens.
Can anyone suggest a workaround?
If this IS a bug, what are the chances of getting it fixed?
______________________________________________________________________
OpenSSL Project http://www.openssl.org
User Support Mailing List openssl-users@openssl.org
Automated List Manager majord...@openssl.org
