[SOLVED] Accidently installed two versions of swi-prolog, need help to fix it

PJvG · 09-27-2013, 06:12 AM

Alright, I have this problem where I installed two different versions of swi-prolog.

I manually installed swi-prolog (swipl) version 5.10.4 from a tar-file, which I see now is a stupid thing. (I can't remember why I did this exactly, but that is besides the point.)

Then I wanted to get the newest version of prolog, so I followed these steps:

Code:

sudo apt-add-repository ppa:swi-prolog/stable
sudo apt-get update
sudo apt-get install swi-prolog

Now if I do

Code:

swipl --version

I get

Code:

SWI-Prolog version 5.10.4 for x86_64-linux

And if I do

Code:

/usr/bin/swipl --version

I get

Code:

SWI-Prolog version 6.4.1 for amd64

I only want the 6.4.1 version on my computer.

I searched the internet for hours, but I couldn't find out how to solve the problem. (Maybe I've been searching for the wrong terms, I don't know.)

Any advice is welcome!
Thanks in advance.

jdkaye · 09-28-2013, 01:27 AM

The version of swi-prolog on my Debian Testing box is 6.4.1-3 and I only have normal Debian repos (not ppa:swi-prolog/stable). I would guess you want to remove the specific swi-prolog stable repo from your sources.list file and then remove all swi-prologs from your system. You can then reinstall swi-prolog from your normal repos and should have only the later version.

I am mystified that you get different results from

Code:

/usr/bin/swipl --version
swipl --version

What does your $PATH variable look like?
On my system I get this:

Code:

~$ swipl --version
SWI-Prolog version 6.4.1 for amd64

jdk

Firerat · 09-28-2013, 03:11 AM

the version from tar is probably installed in /usr/local

confirm with

Code:

which swipl

Did you compile from source, or was it a 'straight' untar ?

if you compiled do you still have the source tree?
if so, cd to it and as root

Code:

make uninstall

if it wasn't compiled ( or the above didn't work for you )
give us the output of

Code:

tar -tf /path/to/prolog.tar

with that listing we can create some kind of script to do the cleanup

PJvG · 10-01-2013, 04:16 AM

jdk, my $PATH variable looks like this:

Code:

bash:
/opt/ros/fuerte/stacks/orocos_toolchain/install/bin:/opt/ros/fuerte/stacks/orocos_toolchain/orogen/bin:/opt/ros/fuerte/stacks/orocos_toolchain/.gems/bin:/opt/ros/fuerte/bin:/usr/lib/ccache:/usr/lib/lightdm/lightdm:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/home/pj/ros/fuerte/tue/trunk/tue_admin_files/common_admin_files/scripts:/home/pj/ros/fuerte/tue/trunk/tue_admin_files/amigo_admin_files/scripts: No such file or directory

Firerat,

Code:

which swipl

produces the following output:

Code:

/usr/local/bin/swipl

I'm pretty sure I compiled from source.

I don't have the .tar anymore, I usually clean up my stuff after downloading.
I can probably download the tar again if I search for it..

The output of

Code:

tar -tf /path/to/prolog.tar

is:

Code:

tar: /path/to/prolog.tar: Cannot open: No such file or directory
tar: Error is not recoverable: exiting now

So, the 5.10.4 version is in /usr/local/bin/, can't I just rm it then? Or is that not clean, e.g. does it leave obsolete files somewhere on disk?

jdkaye · 10-01-2013, 07:39 AM

For the moment you can just delete /usr/local/bin/swipl. That should be enough to guarantee that you will only run the more recent version. In the future you might consider using checkinstall if you compile your own programs. It makes uninstalling them quite easy.
Regarding

Quote:

tar -tf /path/to/prolog.tar

you weren't meant to take "path/to" literally. You were supposed to supply the actual path to where prolog.tar sits on your system.
jdk

PJvG · 10-01-2013, 07:47 AM

Thanks jdk, I used the rm-command and now I get the 6.4.1 version whenever I call swipl.

Yes, I'll try to remember that.

Ah yes, I see my mistake now regarding the tar, I must've been still half-asleep..
Well, like I said, I don't have the .tar-file anymore, but I'm sure I can download it again if needed.

jdkaye · 10-01-2013, 08:41 AM

Excellent! Don't forget to mark this thread as [SOLVED] (Thread Tools menu above your first post on this thread).
thanks,
jdk