Support build with openssl-1.1.x

[takumakume]

This PR will be able to build the ngx_mruby with openssl-1.1.x.

• Support build with openssl-1.1.x (not supported build opt enable-tlsext in openssl-1.1 later)
• Some fixes to CI environment with built-in openssl
  • Upgrade OS to ubuntu:bionic to use libssl-1.1
  • Add environment variable LD, Required here: https://github.com/mruby/mruby/blob/b7af9c47b3f6ec656f7e2d7ee4c1d11cda667748/mrbgems/mruby-bin-mrbc/mrbgem.rake#L12
  • Same modification to Dockerfile.travis_emulate

CI using openssl-1.0.x is gone.
I thought about doing both 1.0 and 1.1, but I thought it would be complicated.

Instead,
I performed a test overwriting this fix with 1.0.2. passed it.
takumakume#1

Pull-Request Check List

• Add patches into src/.
• Add test into test/. Please see about test docs.
• Add docs into docs/ if you change the features such as build system, Ruby methods, class and nginx directives.

[matsumotory]

@takumakume Thank you for your PR. These patches almost look good to me. Could you try to build on Vagrant using ngx_mruby vagrant environment?
And, if you need more patches to Vagrantfile, please write the code.

[takumakume]

@matsumotory

Thank you for check!
I forgot Vagrant.

I confirmed that the test passed with vagrant.

commit: dd51be5

vagrant@vagrant:~/ngx_mruby$ sh test.sh
:
: (snip)
:
Total: 92
   OK: 92
   KO: 0
Crash: 0
 Time: 17.225444 seconds

"[28403] exit worker process from inline code"
"ngx_mruby: STREAM: mruby_stream_exit_worker_code"
ngx_mruby testing ... Done
test.sh ... successful

vagrant@vagrant:~/ngx_mruby$ ./build/nginx/sbin/nginx -V
nginx version: nginx/1.17.4
built by gcc 4.9.3 (Ubuntu 4.9.3-13ubuntu2)
built with OpenSSL 1.1.1  11 Sep 2018
TLS SNI support enabled
configure arguments: --add-module=/home/vagrant/ngx_mruby --add-module=/home/vagrant/ngx_mruby/dependence/ngx_devel_kit --prefix=/home/vagrant/ngx_mruby/build/nginx --with-debug --with-http_stub_status_module --with-http_ssl_module --with-cc-opt='-g -O0' --with-stream --without-stream_access_module

[matsumotory]

Do we need the new openssl test in vagrant?

[matsumotory]

Or ngx_mruby vagrant already supports openssl-1.1.x, right?

[takumakume]

Do we need the new openssl test in vagrant?

As you said.

It may not need for everyone.
I revert it.

Or ngx_mruby vagrant already supports openssl-1.1.x, right?

The current vagrant image is not supported openssl-1.1.x.
using 1.0.2 .

vagrant@vagrant:~/ngx_mruby$ ./build/nginx/sbin/nginx -V
nginx version: nginx/1.17.4
built by gcc 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.11)
built with OpenSSL 1.0.2g  1 Mar 2016
TLS SNI support enabled
configure arguments: --add-module=/home/vagrant/ngx_mruby --add-module=/home/vagrant/ngx_mruby/dependence/ngx_devel_kit --prefix=/home/vagrant/ngx_mruby/build/nginx --with-debug --with-http_stub_status_module --with-http_ssl_module --with-cc-opt='-g -O0' --with-stream --without-stream_access_module

[matsumotory]

If ngx_mruby test supports openssl 1.1.x by default, ngx_mruby vagrant test also should support openssl 1.1.x, or ngx_mruby test supports both openssl 1.0.x and 1.1.x for compatibility.

[matsumotory]

@yyamano How do you think?

[yyamano]

I don't use openssl with ngx_mruby, so no strong opinions.

• Do we want to support both versions of openssl? Supporting multiple versions may increase maintenance cost.
• We should use same version of openssl on travis and vagrant.

[takumakume]

Do we want to support both versions of openssl? Supporting multiple versions may increase maintenance cost.

I agree.
but, openssl-1.0.2 supports up to 2019-12-31..

I am difficult to judge.

If support openssl-1.0.x, be able to test for openssl-1.0.x using the travis matrix .

• Sample code: takumakume/ngx_mruby@supported-openssl-1.1.x...5ff411b
• Test result: https://travis-ci.org/takumakume/ngx_mruby/builds/598630853

We should use same version of openssl on travis and vagrant.

Yes! I understand.

[matsumotory]

@yyamano Thank you for your suggestion. I agree with you. So @takumakume , cloud you implement the vagrant configuration which uses openssl 1.1.x for test as Travis CI?

[takumakume]

So @takumakume , cloud you implement the vagrant configuration which uses openssl 1.1.x for test as Travis CI?

Installed same OpenSSL as Travis CI in vagrant:

vagrant@vagrant:~/ngx_mruby$ openssl version
OpenSSL 1.1.1d  10 Sep 2019

vagrant@vagrant:~/ngx_mruby$ ./build/nginx/sbin/nginx -V
nginx version: nginx/1.17.4
built by gcc 4.9.3 (Ubuntu 4.9.3-13ubuntu2)
built with OpenSSL 1.1.1d  10 Sep 2019
TLS SNI support enabled
configure arguments: --add-module=/home/vagrant/ngx_mruby --add-module=/home/vagrant/ngx_mruby/dependence/ngx_devel_kit --prefix=/home/vagrant/ngx_mruby/build/nginx --with-debug --with-http_stub_status_module --with-http_ssl_module --with-cc-opt='-g -O0' --with-stream --without-stream_access_module

And test passed in vagrant.

commit: 6403fcf

[matsumotory]

Logs are very important.

[matsumotory]

Why do you remove these logs? These logs are important to investigate the error.

Travis limited the number of stdout line, but the local build is no limitation.

[takumakume]

I understand.
Fixed: e88ed19

[matsumotory]

Thank you for your proposal! Merged this PR now.

[takumakume]

Thank you for check!!