<div dir="ltr">If you want to keep 0.9.8, you'll want to get the post-0.9.8y changes that were meant to be part of the 0.9.8za phantom release:<br><br><a href="http://git.openssl.org/gitweb/?p=openssl.git;a=shortlog;h=refs/heads/OpenSSL_0_9_8-stable" target="_blank" rel="noreferrer">http://git.openssl.org/gitweb/?p=openssl.git;a=shortlog;h=refs/heads/OpenSSL_0_9_8-stable</a><br>
<div><br></div><div>When you say you massaged openssl 1.0 to build with gcc, were the only changes made to the build infrastructure in the form included in your mail, or did you have to make code changes? Are you not able to include the linker options, including the maps, with gcc? Why omit the frame pointer?</div>
<div><br></div><div>If you want to continue shipping different release series with 0.9.8, I'd strongly recommend putting it in a separate package so that it can be tracked as a separate dependency for packaged software and can be removed by anyone who doesn't need it and/or judges keeping the older code a greater liability.</div>
</div><div class="gmail_extra"><br><br><div class="gmail_quote">On 14 April 2014 16:31, Alexander Pyhalov <span dir="ltr"><<a href="mailto:alp@rsu.ru" target="_blank">alp@rsu.ru</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hello.<br>
I'm working on enabling openssl-1.0 in oi-userland.<br>
<br>
Please, review this work:<br>
<a href="https://github.com/pyhalov/oi-userland/compare/openssl" target="_blank">https://github.com/pyhalov/oi-<u></u>userland/compare/openssl</a><br>
<br>
The main issue is that we<br>
a) should support legacy software which depends on openssl 0.9.8,<br>
b) can't rebuild the whole OI /hipster .<br>
So, we should provide compatibility package.<br>
<br>
The things I've done:<br>
1) resync our code with userland one,<br>
2) added openssl 0.9.8 auxiliary component (the only target used is "build").<br>
It's used to build libssl.so.0.9.8 and libcrypto.so.0.9.8 after compiling openssl 1.0.<br>
3) massaged openssl 1.0 so that it uses gcc.<br>
<br>
I'm a bit worried that gcc and sun cc build options in Configure script are different. I can't predict how it affects resulting binaries.<br>
<br>
Old Sun Studio config:<br>
"solaris-x86-cc-sunw","cc:-m32 -xO3 -xspace -g -Xa::-D_REENTRANT::-lsocket -lnsl -lc:BN_LLONG RC4_CHAR RC4_CHUNK DES_PTR DES_UNROLL BF_PTR:${x86_elf_asm_sunw}:<u></u>dlfcn:solaris-shared:-KPIC:-<u></u>m32 -G -dy -z text -zdefs -Bdirect -zignore -M/usr/lib/ld/map.pagealign -M/usr/lib/ld/map.noexdata:.<u></u>so.\$(SHLIB_MAJOR).\$(SHLIB_<u></u>MINOR)",<br>
"solaris64-x86_64-cc-sunw","<u></u>cc:-xO3 -m64 -g -xstrconst -Xa -DL_ENDIAN::-D_REENTRANT::-<u></u>lsocket -lnsl -lc:SIXTY_FOUR_BIT_LONG RC4_CHAR RC4_CHUNK BF_PTR DES_PTR DES_INT DES_UNROLL:${x86_64_asm_sunw}:<u></u>dlfcn:solaris-shared:-KPIC:-<u></u>m64 -G -dy -z text -zdefs -Bdirect -zignore -M/usr/lib/ld/map.pagealign -M/usr/lib/ld/map.noexdata:.<u></u>so.\$(SHLIB_MAJOR).\$(SHLIB_<u></u>MINOR)",<br>
<br>
default gcc config:<br>
"solaris-x86-gcc","gcc:-O3 -fomit-frame-pointer -march=pentium -Wall -DL_ENDIAN -DOPENSSL_NO_INLINE_ASM::-D_<u></u>REENTRANT::-lsocket -lnsl -ldl:BN_LLONG ${x86_gcc_des} ${x86_gcc_opts}:${x86_elf_asm}<u></u>:dlfcn:solaris-shared:-fPIC:-<u></u>shared:.so.\$(SHLIB_MAJOR).\$(<u></u>SHLIB_MINOR)",<br>
"solaris64-x86_64-gcc","gcc:-<u></u>m64 -O3 -Wall -DL_ENDIAN -DMD32_REG_T=int::-D_<u></u>REENTRANT::-lsocket -lnsl -ldl:SIXTY_FOUR_BIT_LONG RC4_CHUNK DES_INT DES_UNROLL:${x86_64_asm}:<u></u>dlfcn:solaris-shared:-fPIC:-<u></u>m64 -shared -static-libgcc:.so.\$(SHLIB_<u></u>MAJOR).\$(SHLIB_MINOR)",<br>
<br>
"-ldl" and "-lc" difference doesn't matter, as libdl is just a proxy library for libc. However I can't estimate the influence of other options.<br>
<br>
Testing done:<br>
1) successfully run apache 2.2 (not recompiled) with new openssl 0.9.8 bits,<br>
2) rebuilt and successfully booted latest illumos-gate<br>
3) oi-build rebuild on-going now, so far no surprises<br>
4) found out that apache 2.4 https doesn't work with any openssl (so it's a serious separate issue)<br>
<br>
Waiting for your comments. If I don't receive any negative feedback and userland build completes without issues, I'm going to commit these bits in several few days.<span class="HOEnZb"><font color="#888888"><br>
-- <br>
Best regards,<br>
Alexander Pyhalov,<br>
system administrator of Computer Center of Southern Federal University<br>
<br>
______________________________<u></u>_________________<br>
oi-dev mailing list<br>
<a href="mailto:oi-dev@openindiana.org" target="_blank">oi-dev@openindiana.org</a><br>
<a href="http://openindiana.org/mailman/listinfo/oi-dev" target="_blank">http://openindiana.org/<u></u>mailman/listinfo/oi-dev</a><br>
</font></span></blockquote></div><br></div>