-
-
Notifications
You must be signed in to change notification settings - Fork 247
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
Error: Failed installing dependency: https://luarocks.org/luaossl-20180708-0.src.rock - Could not find header file for CRYPTO #632
Comments
Hey, sorry for not getting back sooner. Most web development frameworks require openssl. PHP is generally compiled with it. If you're using nginx then it's compiled with it (unless you explicitly removed it). The package luaossl expects the openssl package to be installed on your system already, it doesn't compile it's own copy of the openssl source code when installing it. Most Lua packages that use external libraries work this way. This is generally good. Most linuxes have an openssl that is kept up to date by your package manager. You may have to search around in your /usr/local directory to find where openssl is installed, since the directory of the shared libraries may be different depending on the operating system. Hope that helps in your search. |
Spent some time with this issue on Raspberry Pi (RasPi 3 B+). For those seeking a solution: For reference, the error messages were
and
(should help more people locate this solution). |
To add to the above, installing with openresty and luarocks installed via openresty's instructions on Ubuntu, I used |
use where ssl.h use if nothing use
|
Ok so i've spent nearly one day trying to install lapis because of this error and i have to say i'm really pissed off. I don't know where to start but first is that the error message does not mention what should be those headers files (the example shows only CRYPTO_DIR whereas the error message mention INCCRYPTO_DIR). Why not making an install guide? |
apt-get install libssl-dev will do the trick |
A user posted that they were having this problem on OSX 10.15.2, so I tried working through the problem. Here is a log of what I did:
Hope that helps some future visitors. |
On OSX it did pass that error and installing openssl helped to resolve it, but, right after it got broken on installing
any idea how to fix this one? |
@skitsanos, I don't think you can build luabitop on lua 5.3. Maybe try building it on lua 5.1. I posted instructions that would cause you to do that. |
What worked for me (on mac) was making sure I had Lua 5.1 installed then using |
FWIW after Ubuntu 18.04.1 LTS, 5.4.0-56-generic: sudo luarocks install http CRYPTO_LIBDIR=/usr/lib/x86_64-linux-gnu Note LIBDIR not DIR Tested with luajit 2.1.0-beta3 and lua5.1 and h2_streaming.lua all OK. |
Just wanted to chime in, I had this problem when trying to install jitsi-meet-tokens through apt on an x86_64 Debian 11 system. luarocks install luaossl \
CRYPTO_DIR=/usr/include CRYPTO_INCDIR=/usr/include \
CRYPTO_LIBDIR=/usr/lib/x86_64-linux-gnu \
OPENSSL_INCDIR=/usr/include OPENSSL_LIBDIR=/usr/lib/x86_64-linux-gnu Not sure if this is the right / intended way of fixing this, but it worked for my usecase, maybe this will help someone. |
Still having this problem in 2022 on a fresh install of Debian. Ridiculous, clearly the devs don't test their software and just ship it broken. PHP, Django and Flask all don't have this problem, it's only you Lapis. I could probably find some convoluted fix but I recommend people use Sailor instead of Lapis. Development for it is slow but it actually works and is tested before being shipped to people. |
Potentially relevant for future searchers: on Fedora/Oracle Enterprise with OpenResty, using |
On macOS Ventura, I encountered a similar issue when trying to install the
|
I put together some information for mac users: https://gist.github.com/edgarberlinck/c50f4db6d09f6493b1c205a91c2a0264 |
In my case on windows with with find check each location of these
noted them down where they are located which you need to pass as arguments in my case with the paths above
|
So I recently discovered the lapis framework and wanted to try it out. I fired up my Windows machine and set to work. After wrestling with Lua/LuaRocks incompatabilities, I'm greeted with this error:
OK, so it seems like I'm missing OpenSSL, I'll just install that and--
oh.
So it looks like lapis is dependant on luaossl, which is an implementation of OpenSSL which requires binaries of it's source code. This is much too difficult for me to do myself and none of the OpenSSL binaries I've found online have the files wanted by luaossl. Not to worry, I'll just fire up my trusty virtual machine, and make sure to follow the instructions more carefully next time:
This has baffled everyone I've talked to, not least myself. I don't have a copy of Windows 10 Pro (only home edition) so I'm not allowed to use Docker to handle the environment for me. A web development framework requiring OpenSSL is a little alien too (I'm used to CodeIgniter) though I suppose I could get used to it if it wasn't so difficult to install...
Does anyone know what's going on here?
The text was updated successfully, but these errors were encountered: