Pidgin OTR install on Multilib -- Slackware 64 14.1
All,
I have followed aliens Slackware multilib build guide found here to the best of my ability and my goal is to install the pidgin OTR plugin. I first converted the package using the following command Code:
sudo convertpkg-compat32 -i /home/muddy/Downloads/libotr-4.1.0.tar.gz Code:
/tmp/package--compat32/ I then ran Code:
. /etc/profile.d/32dev.sh I changed to the corresponding /tmp/package--compat32 folder that contained my converted libotr package and did a Code:
./configure --prefix=/usr --bindir=/usr/bin/32 Code:
checking for a BSD-compatible install... /usr/bin/ginstall -c When I close Pidgin and re-open I don't find the OTR plugin so it's obviously not installing correctly. Any guidance in this would be appreciated. Hopefully I have provided enough details. |
The first thing you did:
sudo convertpkg-compat32 -i /home/muddy/Downloads/libotr-4.1.0.tar.gz ??? did you mean you tried to convert the source tarball? You do not need to convert the source package because there is no sense in doing so. convertpkg-compat32 command is meant to be used on the 64bit package, produced after configuration and compilation of the sources. Where did you download the libotr-4.1.0.tar.gz file from? On Slackware you typically download the sources tarball of a program (let's say libotr-4.1.0.tar.gz). Then yuo need a Slackbuild script, which will have all the commands in it to detect the environment and to configure, make and make install, and finally produce the package. From what you've done I see that you have configured the sources, then you have to run the command make - to compile the program, and then to make install - in order to install it in your system. But all that is kind of manual compilation and installation, which will make it difficult for you to manage this program in the future (i.e. upgrade, remove). Normally you would download a Slackbuilds pakage, which does not include the sources of the program, extract it somewhere on your system, then download the source tarball, put it in the Slackbuild folder, and from within that folder you would start the slackbuild script as root. The slacbuild script will have a name like libotr.Slackbuild. It will configure, make and make install the program in a temporary folder, and from that folder will produce a tgz or txz package, which then you can install on your system. If that package is 64bit - then you can convert it with the command convertpkg-compat32. The libotr Slackbuild for Slackware 14.1 is here: https://slackbuilds.org/repository/1...raries/libotr/ |
OK, so I finally understand what you mean by that through so much failing. so libotr was successfully installed as per what I received here:
Code:
root@darkstar:/home/muddy/Downloads/libotr# sudo installpkg /tmp/libotr-3.2.0-x86_64-1_SBo.tgz [code] configure: error: libotr 3.2.0 or newer is required. [code] I don't understand why its not finding it. Thanks for any help. |
It's been quite some time from Feb. 18-th.
First let me get something straight - what is your linux distribution? Is it Slackware 14.1 ? 32 bit , or 64 bit? If so, things are somewhat different. As far as I can see at Slackbuilds.org, the Slackbuild scrips for Slackware 14.1 is for libotr-4.1.0 version. But if you check with the site of libotr developers (https://otr.cypherpunks.ca/) - versions 4.1.0 and earlier of libotr in 64-bit builds contain an integer overflow security flaw. Their latest version is libotr-4.1.1 where this flaw has been fixed. At present I am running Slackware 14.2 - current 64 bit + multilib + Eric Hameleers's latest ktown (kde 5). I found that a package from the kde5 set of packages is installed (libotr-4.1.1-x86_64-1alien.txz), and I only had to compile the pidgin-otr package from Slackbuilds.org, which compiled easily and after a restart of pidgin, I can see the otr plugin is available , and working just fine. I have no idea why your pidgin-otr compilation cannot detect your libotr package. It is possible that it has not been built or installed correctly. You have to check the contents of your libotr package and the locations it is supposed to be installed to. If your distribution is 64 bit you do not need to mess with 32 bit converting routines because both libotr and pidgin-otr packages compile and work well on a 64 bit system. But anyway , I am not aware what is exactly your system, and could not be of help to you. |
Quote:
First of all, Thank you so much for your response. I am running 14.1 64bit. I went to the slackbuilds website and found the newest libotr. libotr-4.1.0 which lead to: Code:
Slackware package /tmp/libotr-4.1.0-x86_64-1_SBo.tgz created. Code:
sudo installpkg /tmp/libotr-4.1.0-x86_64-1_SBo.tgz Code:
Package libotr-4.1.0-x86_64-1_SBo.tgz installed. and then installing the latest pidgin-otr package... I'm really not sure why the other one didn't go through. I not even sure where I got that old libotr 3.2.0 version from now. I think I got it from the slackware.com/~alien/ site. But, at any rate... I DO NOW have, the off-the-record plugin listed under pidgin when I go into it now. So thank you thank you thank you! Again I'm not sure what the different is between using the older version of libotr and this 4.1.0 version. If pidgin-otr was unable to find the libotr-3.2.0 version, I'm still not sure why. |
It's good to hear that this has been sorted out.
You can mark the thread [SOLVED] if you think that no more explanation is needed. I cannot help with the previous package compilation missfortunes because I don't know what is the output of the compilation process, nor the contents of the produced package, if any. Good luck! |
All times are GMT -5. The time now is 11:32 PM. |