mirror of
https://github.com/Rigellute/spotify-tui.git
synced 2026-04-27 08:35:58 +03:00
[GH-ISSUE #65] spt: symbol lookup error: spt: undefined symbol: CRYPTO_set_locking_callback #44
Labels
No labels
bug
enhancement
good first issue
help wanted
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/spotify-tui#44
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @rothgar on GitHub (Oct 14, 2019).
Original GitHub issue: https://github.com/Rigellute/spotify-tui/issues/65
I'm on Ubuntu 19.10 and getting this error
I saw other issues with libssl and I fixed my problems from the recommendations in those tickets but still getting this error.
Here's a quick
strace -ff sptI didn't have time to dig into the problem but thought you'd want to know.@Rigellute commented on GitHub (Oct 15, 2019):
Hmm... I 've not seen this exact error before.
Perhaps you've already done this, but could you try this?
@rothgar commented on GitHub (Oct 15, 2019):
Thanks, the system is up to date and rebooted and build-essential is installed. I just did a
cargo install --force spotify-tuiand now I'm back at the libssl errorI already had libssl-dev and pkg-config installed like the other issue recommended.
I don't have that shared library in /lib/x86_64-linux-gnu
I can manually make the symlink but I suspect it's the root of my original problem too (maybe another library also miissing)
@Rigellute commented on GitHub (Oct 15, 2019):
Thanks for the update.
opensslis proving to be quite tricky!This is also what's stopping me from cross compiling from macOS to linux.
@Rigellute commented on GitHub (Jan 26, 2020):
Is this still an issue?
@rothgar commented on GitHub (Jan 27, 2020):
I tried to build it again with cargo and got the same error but I'm able to use the snap package without problems so I'm fine closing this as not reproducible.
@Rigellute commented on GitHub (Jan 29, 2020):
Thanks @rothgar