Ah, I forgot... we changed the requirements to compile that code, from this: # if defined(__GNUC__) && (__GNUC__ > 3 || (__GNUC__ == 3 && __GNUC_MINOR__ >= 1)) to this: # if defined(__SIZEOF_INT128__) && __SIZEOF_INT128__==16 the latter denotes official support while the former was more of a hack, and turned out to be unreliable... There's a bit of discussion on that here: https://github.com/openssl/openssl/issues/6327 So it turns out that your gcc may have the 128-bit extension, but doesn't declare official support for it. Cheers, Richard In message <F4B438E4-C1BC-4A88-A1F2-5A6AAF4627FC@xxxxxxxxxxxx> on Wed, 26 Sep 2018 02:47:51 +0000, Vinay Mummadi <vinay.mummadi@xxxxxxxxxxxx> said: > Hi Richard, > > CC = /u/build/build1/engtools/linux/2.6.18-8.el5/x86_64/gcc/versions/4.3.2/bin/gcc > CXX = /u/build/build1/engtools/linux/2.6.18-8.el5/x86_64/gcc/versions/4.3.2/bin/g++ > > I was using these for openssl 1.1.0h and it compiled with this option " enable-ec_nistp_64_gcc_128" > > Any other possibility, Please suggest. ... > Message: 1 > Date: Mon, 24 Sep 2018 15:42:48 +0200 (CEST) > From: Richard Levitte <levitte@xxxxxxxxxxx> > To: openssl-users@xxxxxxxxxxx > Subject: Re: Build issues with openssl-1.1.1 > Message-ID: <20180924.154248.2078713038705571598.levitte@xxxxxxxxxxx> > Content-Type: Text/Plain; charset=us-ascii > > I'm noticing these from the dump: > > Recorded environment: > > ... > CC = /u/build/build1/engtools/linux/2.6.18-8.el5/x86_64/gcc/versions/4.3.2/bin/gcc > CXX = /u/build/build1/engtools/linux/2.6.18-8.el5/x86_64/gcc/versions/4.3.2/bin/g++ > > Could it be that those compilers don't have support for 128 bit > integers on your platform? In that case, you should remove > 'enable-ec_nistp_64_gcc_128' from your configuration command. > > Cheers, > Richard ... -- openssl-users mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users