Molio-tan commented on issue #4157:
URL: https://github.com/apache/apisix/issues/4157#issuecomment-836580098


   > @Molio-tan Have you tried the similar solution provided by 
https://blog.csdn.net/nange_nice/article/details/82182635? Probably this may 
give you a quick fix.
   > 
   > Currently, only OpenSSL is well tested with openresty. The introduction of 
[GmSSL repository](https://github.com/guanzhi/GmSSL#about-gmssl) tells 
`Existing projects such as Apache web server can be easily ported to GmSSL with 
minor modification and a simple rebuild.`, so maybe there still needs some work 
to get along with openresty.
   > 
   > Since the uncommonly used GmSSL introduces too much complexity and 
uncertainty. Could you use OpenSSL first to check if it works? If everything 
goes well, I guess the only work is to make openresty successfully running on 
GmSSL.
   > 
   > Looking forward to your feedback. Thanks.
   
   I felt SO SORRY that we came back at first on this issue.  The module 
'resty.worker.events' not found.
   Here are my steps:
   1. install openssl111
   ```
   tar -zf openssl-1.1.1h.tar.gz
   cd openssl-1.1.1h/
   ./config --prefix=/usr/local/openssl111 --openssldir=/usr/local/openssl111
   make && make install
   ```
   2. install openresty
   ```
   tar -xzf openresty-1.19.3.1.tar.gz
   cd openresty-1.19.3.1/
   ./configure --prefix=/usr/local/openresty   --with-pcre-jit    --with-ipv6 
--with-http_stub_status_module --without-http_gzip_module 
--with-http_realip_module  --with-http_v2_module
   make && make install
   ln -s /usr/local/openresty/bin/openresty /usr/bin/
   ```
   3. set the path of 'OPENSSL_LIBDIR' and 'OPENSSL_INCDIR' by `luarocks`
   ```
   luarocks config variables.OPENSSL_LIBDIR /usr/local/openssl111/lib
   luarocks config variables.OPENSSL_INCDIR /usr/local/openssl111/include
   ```
   4. start APISIX by `./bin/apisix start`


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to