OpenSSL 1.0.2 transition
Riccardo Mottola
rmottola at opencsw.org
Wed May 3 08:21:40 CEST 2017
Hi Dago,
Dagobert Michelsen wrote:
>> >can I set something different for solaris9? or a value that suits both? I'd like to try there too but it is trying to use a compiler and a target that don't exist.
> Sure, just use
> GARCOMPILER_5.9 = SOS12
> GARCOMPILER_5.10 = SUS12U4
> GARCOMPILER = $(GARCOMPILER_$(GAROSREL))
thanks, I tweaked the lts102 receipe with that - this allows a bit more
progress on solaris 9, although build fails, read below.
I added some further small tweaks and there is now some progress to
report, IT allows me some platform checking:
solaris 9x -> unable to finish build + i386 vs amd64 issues
solaris 9s -> build begins but fails (differently than 9x: pk11 issues)
solaris 10x -> build + test OK
solaris 10s -> build OK, test fail
solaris 11x -> build + test OK
solaris 11s -> buils OK, test fail
So my take is: the code is not SPARC safe, this means in my humble
experience, bad code in terms of structures.. but I see no relevant
patches in the oracle stuff.
Riccardo
PS: regarding solaris9, I see that at least for 9s the issue is pk11, I
noticed that for the old 0.9.8 the configuration appeared optional:
# support for pkcs11 engine
http://blogs.sun.com/chichang1/entry/how_to_integrate_pkcs11_engine
ifdef PKCS11
PACKAGING_PLATFORMS = solaris9-sparc solaris9-i386
solaris10-sparc solaris10-i386
ifneq ($(shell /usr/bin/uname -r),5.9)
PATCHFILES += pkcs11_engine-0.9.8o.patch.2010-09-03
CONFIGURE_ARGS += --pk11-libname=$(abspath
/usr/lib/$(MM_LIBDIR)/libpkcs11.so)
endif
endif
now it is always, has pk11 known issues on solaris9 and should it be
disabled? or am I reading this ifneq(5.9) wrong?
More information about the maintainers
mailing list