Forgot to mention that I am on fips module 2.0.11 fipsld building openssl 1.0.1e with distribution patches when I get the "libcrypto.so.10 is not cross-compiler aware" error. The symbols that incore is looking for are indeed not present (startX etc) in the shared object built. How can I fix this error ?
-----Original Message----- From: openssl-users [mailto:openssl-users-boun...@openssl.org] On Behalf Of Satya Das Sent: Monday, March 28, 2016 5:48 PM To: openssl-users@openssl.org Subject: Re: [openssl-users] Binaries exit with signature bytes >What platform are you building? Is it a native or cross compile? >You'd get that behaviour if fipsld isn't linking the binaries properly. Thanks Steve. I am on centos 6, native compile. I saw " /libcrypto.so is not cross-compiler aware." with fipsld linking until introducing -exe option to incore invocation. It builds fine with the modified fipsld but then I now have this run time error to deal with. TIA. -- openssl-users mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users -- openssl-users mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users
