[openssl.org #1934] Enhancement request: openssl-0.9.8k Solaris CC flags
Old unsupported release, unsupported toolchain. __ OpenSSL Project http://www.openssl.org Development Mailing List openssl-dev@openssl.org Automated List Manager majord...@openssl.org
Re: [openssl.org #1934] Enhancement request: openssl-0.9.8k Solaris CC flags
c^ via RT wrote: Hi all ./Configure solaris64-sparcv9-cc builtin provides the CFLAGS -xtarget=ultra -xarch=v9 This is deprecated in Sun Studio12 and warns a lot. Suggest: -xtarget=ultra2 -m64 -xarch=sparc The -m64 flag doesn't work with Sun Studio 10 compilers, so it will simply break in this case. I came to the same problem and the solution was to patch the Configure and replace those fixed directives with something like \$(CC_ARCH_FLAGS) and then use CC_ARCH_FLAGS=-m64 make ... for SunStudio11+ and CC_ARCH_FLAGS=-xtarget=ultra -xarch=v9 make ... for SunStudio10 The proper solution would be to check the CC version and set those flags accordingly. I somehow doubt this is wise thing to do, cause who knows what SunCC will break in the next release ;) Regards -- ^(TM) __ OpenSSL Project http://www.openssl.org Development Mailing List openssl-dev@openssl.org Automated List Manager majord...@openssl.org
[openssl.org #1934] Enhancement request: openssl-0.9.8k Solaris CC flags
Hi all ./Configure solaris64-sparcv9-cc builtin provides the CFLAGS -xtarget=ultra -xarch=v9 This is deprecated in Sun Studio12 and warns a lot. Suggest: -xtarget=ultra2 -m64 -xarch=sparc as a good set of defaults to replace this. First ultra2 cpu's shipped in 1999 and last ultras in 2000. So probably ok to optimise for ultra2 these days. The more aggresive may go for -xtarget=ultra3, however I still have ultra2's in service. Many thanks CraigT -- c^ [c%5e] Even when you are standing in front of defeat, do it smiling. __ OpenSSL Project http://www.openssl.org Development Mailing List openssl-dev@openssl.org Automated List Manager majord...@openssl.org
