complie failed on CentOS 7

[kn007]

make install failed on CentOS 7 x64(kernel 4.9.86-30) with gcc 7.3.1 20180303

install libcrypto.a -> /data/src/openssl/.openssl/lib/libcrypto.a
install libssl.a -> /data/src/openssl/.openssl/lib/libssl.a
install libcrypto.so.1.1 -> /data/src/openssl/.openssl/lib/libcrypto.so.1.1
link /data/src/openssl/.openssl/lib/libcrypto.so -> /data/src/openssl/.openssl/lib/libcrypto.so.1.1
install libcrypto.so -> /data/src/openssl/.openssl/lib/libcrypto.so
install libcrypto.so.1.1 -> /data/src/openssl/.openssl/lib/libcrypto.so
ar: /data/src/openssl/.openssl/lib/libcrypto.so: File format not recognized
ar: /data/src/openssl/.openssl/lib/libcrypto.so.new: File format not recognized
make: *** [Makefile:328: install_dev] Error 1

[levitte]

That's curious... Would you mind showing us your configuration command? The output of this should do:

perl configdata.pm -c

[kn007]

 perl configdata.pm -c                                                                                      master [dfee862] modified untracked

Command line (with current working directory = .):

    /usr/bin/perl ./Configure linux-x86_64 --prefix=/data/src/openssl/.openssl --openssldir=/etc/pki/tls shared zlib-dynamic enable-tls1_3 enable-weak-ssl-ciphers enable-ec_nistp_64_gcc_128

Perl information:

    /usr/bin/perl
    5.16.3 for x86_64-linux-thread-multi

[richsalz]

@kn007 He meant the output of running perl configdata. (And . is always the name of the current working directory :)

[kn007]

@richsalz Yes, it is the result of the perl configdata.pm -c

[richsalz]

So it generated no output? Strange.

[kn007]

The output is here: #6641 (comment)

[richsalz]

okay, thanks (I mis-read it). @levitte will have to look at this.

[kn007]

Thank you.

Which gcc version is recommand to compile openssl?

[levitte]

The trouble with this is that the Makefile seems to be generated for AIX. AIX is a strange beast in many regards, and the Makefile for it contains code that stuffs libcrypto.so into libcrypto.a (long story). This shouldn't appear anywhere else, but it seems like it did in your case, hence the ar error messages that you see.

@dot-asm, you did the AIX work, do you have any idea what happened here?

[levitte]

It might be that my guess is wrong as well. Looking further...

[dot-asm]

@dot-asm, you did the AIX work, do you have any idea what happened here?

No. And I can't see that one should blame AIX support. Because if it went that road, i.e. AIX-specific Makefile generated in reply to linux-x86_64, then ar wouldn't complain with "File format not recognized", it would create archive file.

[levitte]

Well, in that case, I'm out of ideas. @kn007, would you mind sharing the produced Makefile?

[kn007]

Sure, Makefile.zip

[levitte]

... and looking at that, I found exactly the AIX stuff that I suspected!

[levitte]

(look for strip -X32_64, the suspected code surrounds that line)

[dot-asm]

Then question is how come did it emit AIX-specific segment in reply to Configure linux-x86_64. It should noted that there are three target-specific segments, Linux, mingw and AIX. All three seem to be emitted. So it boils down to output_on/output_off thing, i.e. back to you:-) Let's keep in mind that make install is exercised by travis on per-push basis, on Linux and Mac OS X.

[levitte]

Ah, I looked through the changelog for Text::Template, and the changes indicate that Text::Template->append_text_to_output came in version 1.46. That means that any version older than that will fail in exactly this way (i.e. output_off and output_on have no effect).

[levitte]

So I suppose that @kn007 has an older Text::Template, which can be confirmed like this:

perl -e 'use Text::Template; print $Text::Template::VERSION,"\n";'

[kn007]

Thank you, it is 1.45.
Let me try to upgrade it and complie openssl again.

[kn007]

After Text::Template upgrade to 1.53, openssl compile fine, thanks a lot.

[nathancfox]

@kn007 Hi, I just ran into the same issue in a different setting and my Text::Template is also 1.45. How did you upgrade yours to fix the issue?

[kn007]

using cpan to upgrade it.
other way you could compile it by yourself.

[AbleSteven]

Thank you, you save my life ! @levitte