building openssl 1.1.1 for Solaris 10
tim.j.culhane at gmail.com
tim.j.culhane at gmail.com
Mon Apr 6 15:14:38 UTC 2020
Hi,
I'm using gcc 4.9.2
So, should I just ignore that warning and let the gmake continue?
Tim
-----Original Message-----
From: openssl-users <openssl-users-bounces at openssl.org> On Behalf Of Michael
Wojcik
Sent: Monday 6 April 2020 15:31
To: openssl-users at openssl.org
Subject: RE: building openssl 1.1.1 for Solaris 10
> From: tim.j.culhane at gmail.com [mailto:tim.j.culhane at gmail.com]
> Sent: Monday, April 06, 2020 06:35
> To: Michael Wojcik; openssl-users at openssl.org
> Subject: RE: building openssl 1.1.1 for Solaris 10
>
> Ok, attempting to build openssl 1.1.1e now.
>
> As prompted by the config script I'm running Configure as follows:
>
> ./Configure solaris64-sparcv9-cc --prefix=/opt/openssl/1.1.1
> --openssldir=/opt/openssl/1.1.1
>
> That completes successfully. However, when I then run gmake I see
> warnings like the below:
>
>
> cc: Warning: -xarch=v9 is deprecated, use -m64 to create 64-bit
> programs
>
> How can I configure the makefiles so they use '-m64'.
As far as I know you can't, except by editing Configurations/10-main.conf
(one of the inputs to the Configure script). The -xarch=... flags are
hard-coded there.
Personally I wouldn't worry about it. -xarch is deprecated, but it still
works. (And -m64 is not, as I understand it, exactly equivalent to -xarch
anyway. I'm a bit suspicious of that warning from cc; I'd think you'd want
-mcpu=... as well as -m64. But I haven't looked at the Sun C compiler
options for some years.)
What version of the C compiler are you using? Note these comments in
10-main.conf:
# SC4.0 doesn't pass 'make test', upgrade to SC5.0 or SC4.2.
# SC4.2 is ok, better than gcc even on bn as long as you tell it -xarch=v8 #
SC5.0 note: Compiler common patch 107357-01 or later is required!
Some people prefer to use gcc on Solaris for this reason.
--
Michael Wojcik
Distinguished Engineer, Micro Focus
More information about the openssl-users
mailing list