-
Notifications
You must be signed in to change notification settings - Fork 3k
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
can't find libsecp256k1 library error #5606
Comments
I just encountered this also. To make it work, I had to install as per these instructions: |
Also see https://github.com/spesmilo/electrum-docs/blob/master/libsecp256k1-linux.rst Note: since merging the lightning branch, libsecp256k1 became a mandatory dependency (was optional before). The README was not updated since.
|
Thanks! It's working now. |
Oh, I should probably leave this open... |
Did this in 251db63 for now |
yes let's make it mandatory |
it would be possible to list it as a python dependency, see https://github.com/electrumsv/electrumsv-secp256k1 |
a lazy solution will be: sudo apt install libsecp256k1-dev |
build / run fails because of this. It should be mentioned in the readme, or fixed internally to drag this lib in during install. |
Can we get the option to build without lightning? Have no interest in using that, ever. |
What exactly do you mean? The topic of this thread is whether to make libsecp256k1 a mandatory dependency. |
Hmmmmmmm, I'm running into an error here:
I don't know how to bypass it. I have installed libsecp256k1 on my system. libsecp256k1.s.0 is in /usr/local/lib. I can't run the new version from a clean build. What do I do? |
That's a warning, not an error. |
@Thecreator1 If you use the AppImage (or Mac/Windows binaries), there are no dependencies. It is self-contained. If you use the source tarball, it only contains python sources. It does not contain the non-pure-python dependencies. |
I still get the error. It seems that pip installs an empty package:
Also, the given home page is empty. This makes electrum-4.0.9 unusable. |
It's not a warning if you can't build because of it, it's an error. Users should never need access to /usr/lib, so it should look in /usr/local/lib for any libs it needs for a normal user install. |
I ran all of the installation instructions in the development version's README, but I got this error.
I have bitcoin core v0.18 installed, so shouldn't I have libsecp256k1 installed?
The text was updated successfully, but these errors were encountered: