On Thu, Jan 09, 2003 at 05:34:39PM +0100, Andy Polyakov wrote: > > Btw., does anybody have an idea where a symbol ".RC4_end" could come from? > > I should have an idea... To start which I didn't expect to see .RC4_end > symbol be visible at all. Assembler should have hidden it as names > starting with . are supposed to be internal. I can double-check it later > today. As for dropped RC4 symbol. I'm not really following... Did 'make > test' pass?
No. The problem is that when creating the link stub, the _RC4 symbol is treated as a data or bss symbol, not a text symbol. Linking against that link stub creates an illegal reference into the DLL ==> rc4test crashes. The same happens with _DES_ede3_cbc_encrypt and _DES_ncbc_encrypt, resulting in destest crashing. This all doesn't happen when linking against the static crypto lib, btw., it's justy a problem of the dynamic linking process. > > c=`echo $$i | sed 's/^lib\(.*\).dll/cyg\1-$(SHLIB_VERSION_NUMBER).dll/'`; > ^ this of course works, but it probably > should be \., not just dot:-) Oops, you're right. Thanks, Corinna -- Corinna Vinschen Cygwin Developer Red Hat, Inc. mailto:[EMAIL PROTECTED] ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
