Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

installation from source: missing dependency: luasec, libpcre3-dev #24

Closed
ahmadnassri opened this issue Feb 20, 2015 · 12 comments
Closed

Comments

@ahmadnassri
Copy link
Contributor

luasec

failed at:

Error: Failed installing dependency: http://luarocks.org/repositories/rocks/busted-2.0.rc6-0.rockspec - Failed installing dependency: http://luarocks.org/repositories/rocks/mediator_lua-1.1-3.rockspec - Error fetching file: Failed downloading https://github.com/Olivine-Labs/mediator_lua/archive/v1.1.tar.gz - Unsupported protocol - install luasec to get HTTPS support.

attempting to install with:

sudo luarocks install luasec

results in the following error:

Error: Could not find expected file libssl.a, or libssl.so, or libssl.so.* for OPENSSL -- you may have to install OPENSSL in your system and/or pass OPENSSL_DIR or OPENSSL_LIBDIR to the luarocks command. Example: luarocks install luasec OPENSSL_DIR=/usr/local

this is resolved with:

sudo luarocks install luasec OPENSSL_LIBDIR=/usr/lib/`gcc -print-multiarch`

libpcre3-dev

failed at:

Error: Failed installing dependency: http://luarocks.org/repositories/rocks/lrexlib-pcre-2.7.2-1.src.rock - Could not find expected file pcre.h for PCRE -- you may have to install PCRE in your system and/or pass PCRE_DIR or PCRE_INCDIR to the luarocks command. Example: luarocks install lrexlib-pcre PCRE_DIR=/usr/local

this is resolved with:

sudo apt-get install libpcre3-dev
@subnetmarco
Copy link
Member

@ahmadnassri On MacOSX ?

@ahmadnassri
Copy link
Contributor Author

@thefosk no Linux!

@nijikokun
Copy link
Contributor

What is the Linux Distro and Version are you doing this on?

@ahmadnassri
Copy link
Contributor Author

Linux Mint 17.1

@subnetmarco
Copy link
Member

I've updated the dependencies list in the README file. We require also pcre-devel and openssl-devel to successfully build the project.

@thibaultcha thibaultcha changed the title installation from source: missing dependency: luasec installation from source: missing dependency: luasec, libpcre3-dev Feb 23, 2015
@thibaultcha
Copy link
Member

They have been added to the README but not all platforms need it. We need a different approach:

Install

Linux

OS X

etc...

This way we could also avoid finding manually the correct libs and let the user specify it. After all, that's how everybody does it, we shouldn't make decisions instead of the user. Same for the force usage of sudo.

@subnetmarco
Copy link
Member

We need something that can automatically install dependencies. Once Kong is being released in rpm or deb format it's going to be easier to install everything since the installation package will also automatically install the dependencies.

Right now I'm pretty sure the README dependencies list is not complete too.

@thibaultcha
Copy link
Member

We need to install dependencies only if those are not built-in in the system we are installing it in. In OS X, no need to install those libs. In debian, need to install them through apt-get, in CentOS, probably with yum, etc...

@subnetmarco
Copy link
Member

By using a package manager if the dependencies are already installed they won't be reinstalled.

@thibaultcha
Copy link
Member

How do you know which package manager to use? How do you know if the dependency is not already installed for this platform?

We need to just specify platform-specific installation processes. Like... Everybody else in the world.

@thibaultcha
Copy link
Member

Installation from source with OS X + Homebrew is now entirely documented: ddfc482

@thibaultcha
Copy link
Member

We now know what is needed to install kong, and we will update our INSTALL.md with missing platforms.

anonymouse64 added a commit to anonymouse64/kong-snap that referenced this issue Jun 27, 2018
gszr pushed a commit that referenced this issue Jun 10, 2021
Plugins in Kong are being moved over to the
new DAO for 0.15.0/1.0.0 release.
This commit makes misc changes to make
use of the new DAO layer.

The changes also include using Kong PDK functions
where possible.

Changes:
- Update schema.lua to the new plugin schema syntax
- Translate several ngx.* calls to kong.* calls, using the new PDK
   (not all of them are translatable just yet).
- The prometheus/prometheus.lua vendored dependency 
   has been left untouched.
- The api.lua file has also been updated to support
   new DAO and auto-generated endpoints, (whic
   are not used in case of this plugin).

From #24
gszr pushed a commit that referenced this issue Jun 10, 2021
#24 introduced issues after porting to new DAO.
This change fixes the following:

- kong.log.err/warn instead of ERR/WARN
- usage of responses.lua instead of kong.response.exit
- unnecessary use of the consumer's schema in api.lua

From #26
gszr pushed a commit that referenced this issue Jul 7, 2021
Two endpoints exist at this time:

POST /acme create a certificate or test the Kong setup to create
this certificate.

PATCH /acme triggers the renewal timer, the plugin will decide which
certificates to renew.
gszr pushed a commit that referenced this issue Aug 6, 2021
Plugins in Kong are being moved over to the
new DAO for 0.15.0/1.0.0 release.
This commit makes misc changes to make
use of the new DAO layer.

The changes also include using Kong PDK functions
where possible.

Changes:
- Update schema.lua to the new plugin schema syntax
- Translate several ngx.* calls to kong.* calls, using the new PDK
   (not all of them are translatable just yet).
- The prometheus/prometheus.lua vendored dependency
   has been left untouched.
- The api.lua file has also been updated to support
   new DAO and auto-generated endpoints, (whic
   are not used in case of this plugin).

From #24
gszr pushed a commit that referenced this issue Oct 26, 2021
gszr pushed a commit that referenced this issue Oct 27, 2021
gszr pushed a commit that referenced this issue Oct 28, 2021
…strings (#24)

Short circuit mechanism for un-configured request transformer using
query strings was improperly checking the `rename` query string
configuration contents. This caused reserved words that should have
remained un-encoded to be URL encoded by the unnecessary transform.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants