> I could not get this working even on a 11.23 machine having latest (last > one released in December 2007).
... latest what? I mean it appears that you missed something. But more relevant question is what does ld -V return, what patches are installed. But please don't show the list and ask which patches should be installed. Or at least don't expect answer from me, as I don't know. As already mentioned, the references to specific ld versions is simply something that was observed to not work and then work in specific situation, it's just two dots on the mesh, that's all. > Can anyone tell me the impact of not using +sectionmerge since it is not > working on 11.23. It was mentioned it the beginning of thread: "it didn't do the sectionmerge (*which was resulting in crash upon startup*)". It should be noted that crash is one possibility, another possibility is that initialization test is rendered *non-compliant* with validation requirements. > I am also evaluating the possibility of using 11.31 and tried building > openssl on it, however, getting different error while bulding fips code > this time: > > + cc -I. -I.. -I../include -DOPENSSL_FIPSCANISTER +Z -DOPENSSL_PIC > -DOPENSSL_THREADS -DDSO_DLFCN -DHAVE_DLFCN_H -D_REENTRANT -Ae +DD64 +O3 > (Bundled) cc: warning 922: ^^^^^^^^^ Real, i.e. unbundled, compiler is absolute requirement for OpenSSL on HP-UX in any situation. > Another build issue on HP-PA: > I am getting following error on HP-PA while building fips capable openssl: > > make[2]: Entering directory `/openssl/hp-pa/openssl-1.0.1h' > [ -z "libcrypto" ] || cc +Z -DOPENSSL_PIC -DOPENSSL_THREADS -DDSO_DL > -D_REENTRANT +DA2.0 +DS2.0 +O3 +Optrs_strongly_typed -Ae +ESlit > -DB_ENDIAN -DMD32_XARRAY -D_REENTRANT -I/openssl/hp-pa/fips/include > -Iinclude \ > -DFINGERPRINT_PREMAIN_DSO_LOAD -o fips_premain_dso \ > /openssl/hp-pa/fips/lib/fips_premain.c > /openssl/hp-pa/fips/lib/fipscanister.o \ > libcrypto.a -Wl,+s -ldld > /usr/ccs/bin/ld: Duplicate symbol "$global$" in files > /opt/langtools/lib/crt0.o and /openssl/hp-pa/fips/lib/fipscanister.o I don't have comment on this, because I don't have access to HP-PA system with vendor compiler. I can only say that goal is that fipscanister.o looks exactly like any other .o file generated by compiler, and just like any other such file it shouldn't have symbols otherwise found in crt0.o. The fact that crt0.o symbols made their way to fipscanister.o indicates that something went wrong at fipscanister.o link stage and -r flag was not respected. Is it possible that it also was linked with bundled compiler? ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List openssl-dev@openssl.org Automated List Manager majord...@openssl.org
