I just wanted to make sure that the last, successful modification for aix64-cc shared build (-bautoexp, not *.exp files) is now acceptable (as well as for aic43-cc) for you. About gcc, the problem remains but I was unable to find the solution. Anyway, I am skeptical about gcc on aix because aix-gcc/aix43-gcc built static libraries do not properly link with C++ modules (built by xlC) - this was not a problem on solaris and linux.
Regards, Vladimir -----Original Message----- From: Shklover, Vladimir Sent: Tuesday, January 21, 2003 10:44 AM To: '[EMAIL PROTECTED]' Cc: [EMAIL PROTECTED] Subject: RE: [openssl.org #463] PATCH 1)I just got aix64-cc shared build succeed with -bautoexp. It was possible to modify Makefile pretty similar to aix43-cc. ******************************************************************* SHARED_LDFLAGS=-q64 ................................................................... # AIX: $(CC) ALLSYMSFLAG=-bnogc SHAREDFLAGS=${SHARED_LDFLAGS} -G -bautoexp -bM:SRE SHAREDCMD=$(CC) do_aix-shared: libs='-L. ${SHLIBDEPS}'; for i in ${SHLIBDIRS}; do \ ( set -x; \ ld -b64 -r -o lib$$i.o $(ALLSYMSFLAG) lib$$i.a && \ ( \ $(SHAREDCMD) $(SHAREDFLAGS) \ -o lib$$i.so.${SHLIB_MAJOR}.${SHLIB_MINOR} lib$$i.o \ $$libs ${EX_LIBS} ) ) \ || exit 1; \ libs="$$libs -l$$i"; \ done ******************************************************************** Therefore, for both 32 and 64 bits we can now build shared libraries with -bautoexp as well as with *.exp files. 2)You are right, the version openssl-0.9.7 did not contain 0.9.7 extention for aix but in my changes (which appear to be in snapshot version) I included these extentions to be consistent with other platforms where shared build contain these extention. I made experimental builds without extentions just for myself; I didn't send you such changes to Makefile. The reason I did that for myself is that if you link a module, say module.so with soname libcrypto.so.0.9.6, you can not then dynamically load it with libcrypto.so.0.9.7. However, if you link module.so with libcrypto.so (by modified Makefile from, say, openssl-0.9.6), you can dynamically load it with either version as they have symbolic links to libcrypto.so (we are not physically including libssl.so... & libcrypto.so... into our software and SSL connection will work if the user installs openssl himself). On solaris and linux it worked, but on aix caused problems (I didn't check for Windows yest but expect it should work). But this is not so important at that time, you don't have to worry. Vladimir -----Original Message----- From: Andy Polyakov via RT [mailto:[EMAIL PROTECTED]] Sent: Tuesday, January 21, 2003 9:51 AM To: Shklover, Vladimir Cc: [EMAIL PROTECTED] Subject: Re: [openssl.org #463] PATCH As you don't appear to be interested in 64-bit build I've decided to settle for following. We leave the code as is [as in openssl-0.9.7-stable-SNAP-20030119.tar.gz or later] and document the aix64-cc case in PROBLEMS in wait for more appropriate solution (covering even gcc:-). BTW. Can use verify if following works: - ./Configure aix64-cc shared; - env OBJECT_MODE=64 make; > > 2)On AIX modulenames contain *.so.0.9.7 as well as on other platforms. > > However, it is easy to change Makefile so that they were named just *.so > > which I did. > > ??? Makefile.org in 0.9.7 says -o lib$$i.so, i.e. no .0.9.7 is appended. > Two sentences above don't make any sense to me, unless you asked us to > change it earlier, before 0.9.7 release that is. Please clarify. But I still want to hear about this. Cheers. A. ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]