Hi, Just to say that you can get the -Fpic flag by using the 'shared' argument to the Configure script. The following works for me: ./Configure solaris64-sparcv9-cc --prefix=/opt/openssl/1.1.1 --openssldir=/opt/openssl/1.1.1 -lrt -m64 shared zlib Regards, Tim -----Original Message----- From: openssl-users <openssl-users-bounces@xxxxxxxxxxx> On Behalf Of Michael Wojcik Sent: Thursday 16 April 2020 18:16 To: openssl-users@xxxxxxxxxxx Subject: RE: building a PIC enabled version of openssl 1.0.2k on Sparc 10 > From: openssl-users [mailto:openssl-users-bounces@xxxxxxxxxxx] On > Behalf Of tim.j.culhane@xxxxxxxxx > Sent: Thursday, April 16, 2020 08:36 > > I'm building a PIC enabled shared library in my server which links > against openssl 1.0.2k libssl.a library on Sparc 10. > > When compiling I see the below errors. > > I originally built the 1.0.2k version of openssl with the following > configure arguments: > > ./Configure solaris64-sparcv9-cc --prefix=/opt/openssl/1.0.2k > --openssldir=/opt/openssl/1.0.2k -lrt -m64 > > Do I need to pass in the -fPIC flag as well, and if so how do I do that. I believe you do, though our use case is different - we build OpenSSL as a PIC archive library, which we then linked into a shared object. If you're building OpenSSL as a shared object (well, a pair of shared objects, for libcrypto and libssl), then you may be able to do that with the appropriate Configure options. My teams have switched to 1.1.1, so I don't have a 1.0.2 build handy to check. > I appended it to the end of the configure line I show above but > there was no sign of PIC in any of the top level makefiles produced. For 1.0.2, we edited the Configure file. We kept a log of the purposes of our changes, and looked at the Configure diffs for each new 1.0.2 release so we could port the relevant changes back to our Configure. We haven't had to do that with 1.1.1; its Configure is more flexible. -- Michael Wojcik Distinguished Engineer, Micro Focus
