Steven, You are right again - as always.
I checked the HP's code and indeed, they use $ USER_CCFLAGS == "/pointer_size=64" This means that the HP SSL product really does deliver both 32 and 64 bit libraries. It would be fruitful, if somebody competent could look into the HP's code and see how they solved the 64-bit descriptors issue. Regards, Z -----Original Message----- From: Steven M. Schweda [mailto:s...@antinode.info] Sent: den 15 februari 2011 16:14 To: openssl-dev@openssl.org Subject: Re: [openssl.org #2449] [BUG] openssl 1.0.0d warnings during build and ACCVIO on OpenVMS From: Arpadffy Zoltan <zoltan.arpad...@scientificgames.se> > > Why have a build option which doesn't work? > > Actually, it works good enough to keep, as we can still use the following o= > ptions: > - 32 for build with /POINTER_SIZE=3D32 - that is used often together with o= > lder applications. > - "" for build with default /NOPOINTER_SIZE (that is definitely not compati= > ble nor exchangeable with /POINTER_SIZE=3D32 built libraries. A library built using /POINTER_SIZE=32 is _not_ the same as one built using /NOPOINTER_SIZE? Really? I can see where /POINTER_SIZE=64 would be different. How is /POINTER_SIZE=32 different? (I can also see where it might be important to say /POINTER_SIZE=64=ARGV, when building a main program with 64-bit pointers, too.) > Therefore, the important thing that is needed to be noted for such dummy dr= > eamers like me, that parameter 64 is not equal to parameter "" - and those = > two are not exchangeable. Perhaps everyone else reads the HELP (or the other documentation). > Hmmm also make a side note, that the current OpenSSL code is not able to be= > built with full 64-bit pointer size option - but as we lived so far withou= > t it - we can continue to use the OpenSSL libraries as it is, until somebod= > y really needs 64-bit pointer size. Define "we". HP supplies SSL$LIBCRYPTO_SHR.EXE, SSL$LIBCRYPTO_SHR32.EXE, SSL$LIBSSL_SHR.EXE, and SSL$LIBSSL_SHR32.EXE. I thought that the whole idea was to get the OpenSSL builder(s) to create SSL_LIBCRYPTO_SHR.EXE/OLB, SSL_LIBCRYPTO_SHR32.EXE/OLB, SSL_LIBSSL_SHR.EXE/OLB, and SSL_LIBSSL_SHR32.EXE/OLB, that is, 32- and 64-bit libraries and shared images. (Even if no one wanted to add the "SSL_" prefixes.) Did I miss something? ------------------------------------------------------------------------ Steven M. Schweda sms@antinode-info 382 South Warwick Street (+1) 651-699-9818 Saint Paul MN 55105-2547 ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List openssl-dev@openssl.org Automated List Manager majord...@openssl.org ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List openssl-dev@openssl.org Automated List Manager majord...@openssl.org
