VectorLinux

The nuts and bolts => Office & Printing => Topic started by: lagagnon on December 29, 2007, 12:03:30 pm

Title: Abiword libiconv Error after removing wv....
Post by: lagagnon on December 29, 2007, 12:03:30 pm
I seem to have done something silly by removing the packages "wv and wv2". These seemed superfluous but now  I discover they are used by AbiWord to convert MS .doc files. I re-installed them but now get the error:

abiword: error while loading shared libraries: libiconv.so.2: cannot open shared object file: No such file or directory

I attempted to re-install Abiword, but to no avail. There is a post here about libiconv no longer in use on 5.9:
http://www.vectorlinux.com/forum2/index.php?topic=4262.0

Can someone assist me on how to get rid of this strange error? I am a bit lost as to where to start....

Title: Re: Abiword libiconv Error after removing wv....
Post by: uelsk8s on December 29, 2007, 12:39:08 pm
where did you get the wv package from?
it looks like it was built before libiconv was removed
Title: Re: Abiword libiconv Error after removing wv....
Post by: lagagnon on December 29, 2007, 02:46:08 pm
where did you get the wv package from?
it looks like it was built before libiconv was removed
It was the inbuilt VL5.9 Gold package - I did no upgrades, or anything else. Very strange...
Title: Re: Abiword libiconv Error after removing wv....
Post by: uelsk8s on December 29, 2007, 02:59:51 pm
can you try reinstalling them with slapt-get and see if it helps?
Title: Re: Abiword libiconv Error after removing wv....
Post by: lagagnon on December 29, 2007, 03:45:46 pm
ok, reinstalled wv and abiword with slapt-get after doing a clean and all OK now. Strange, but my hearty thanks !!!
Title: Re: Abiword libiconv Error after removing wv....
Post by: uelsk8s on December 29, 2007, 04:18:23 pm
whew  :)
Title: Re: Abiword libiconv Error after removing wv....
Post by: Triarius Fidelis on December 29, 2007, 05:17:32 pm
ok, reinstalled wv and abiword with slapt-get after doing a clean and all OK now. Strange, but my hearty thanks !!!

Maybe something weird with library caching.