SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Problem:
I want to build profanity with omemo support.
I use slackbuild but I give it latest profanity release from github
and it builds if I do not change slackbuild. If I add --enable-omemo, then I can see the following stuff
Code:
checking for libsignal... no
configure: libsignal >= 2.3.2 not found, checking for libsignal 2.3.x...
checking for libsignal... no
configure: error: libsignal-protocol-c is required for OMEMO support
Last edited by unInstance; 02-14-2020 at 02:29 PM.
If you want to build it with omemo support, you will have to build yourself a package for libsignal-protocol-c from the source files here as the is no SlackBuilkd for it @ https://slackbuilds.org/. Good luck.
If you want to build it with omemo support, you will have to build yourself a package for libsignal-protocol-c from the source files here as the is no SlackBuilkd for it @ https://slackbuilds.org/. Good luck.
I wrote that i did it. But profanity does not see it.
I wrote that i did it. But profanity does not see it.
Sorry for my distraction. But then, how/where is it installed? To be sure, please type as root:
updatedb
then provide the output of:
locate libsignal.so
Just as an FYI, I created a Slackbuild for libsignal-protocol-c last year when I was playing around with profanity. I did not submit to slackbuilds.org because the version of profanity there does not support OMEMO. Therefore I thought that there is probably no demand for libsignal-protocol-c. Since this came up now I did submit the Slackbuild. With any luck it will show up over the weekend. If you want you can click on "My Slackbuilds" in my signature and download the Slackbuild from there.
I was able to successfully run ./configure with this for profanity version 0.8.1. The build itself fails at a later stage, though, but maybe we can take this one step at a time.
UPDATE: I have successfully build profanity 0.8.1 with './configure --enable-omemo'. You write that you are using Slackware 5.4.13. I assume that is Slackware current? I have build on Slackware 14.2.
Please let me know if the Slackbuild (libsignal-protocol-c) works for you.
Sorry for my distraction. But then, how/where is it installed? To be sure, please type as root:
updatedb
then provide the output of:
locate libsignal.so
No locate output.
This is what make install installs:
UPDATE: I have successfully build profanity 0.8.1 with './configure --enable-omemo'. You write that you are using Slackware 5.4.13. I assume that is Slackware current? I have build on Slackware 14.2.
Please let me know if the Slackbuild (libsignal-protocol-c) works for you.
Yes, I am indeed on current. Your slackbuild works! I managed to build latest profanity with omemo support.
Looks like I installed libsignal-protocol-c in a wrong way. I should have specified how I did it.
Thank you. Everything works.
Last edited by unInstance; 02-15-2020 at 11:03 AM.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.