Re: abiword installation problem on Linux

Thanks for your reply, Alan. Unfortunately, I'm still stuck.

I tried installing enchant using the package manager and I got the
following error:

$ rpm -i enchant-1.3.0-1.fc6.i386.rpm
warning: enchant-1.3.0-1.fc6.i386.rpm: V3 DSA signature: NOKEY, key ID
1ac70ce6
error: Failed dependencies:
         libc.so.6(GLIBC_2.4) is needed by enchant-1.3.0-1.fc6.i386
         rtld(GNU_HASH) is needed by enchant-1.3.0-1.fc6.i386

so I downloaded and tried to install the libc rpm and got the following
error:

$ rpm -i glibc-2.3.6-4.i386.rpm
warning: glibc-2.3.6-4.i386.rpm: V3 DSA signature: NOKEY, key ID 30c9ecf8
error: Failed dependencies:
         glibc-common = 2.3.6-4 is needed by glibc-2.3.6-4.i386
         glibc > 2.3.4 conflicts with glibc-common-2.3.4-2.9.i386

I could spend the rest of the day (optimistic estimate) trying to resolve
these problems but the thing is that enchant installed fine using the
tarball. Is there no way to get abiword to be happy with the tarball
version of enchant?

Thanks,
Will

On Thu, 8 Feb 2007, Alan Horkan wrote:

> On Wed, 7 Feb 2007, Willem van Heiningen wrote:
>
>> I'm running Red Hat Enterprise Linux WS release 4 (Nahant Update 1).
>>
>> When I try to install abiword (abiword-2.4.5.x86.package)
>
> Note: that is an Autopackage
>
>> on my laptop I get
>> the following error message:
>>
>> ------------------------------------------------------------------------
>> Error: Could not find 'Enchant is a cross-platform abstract layer to
>> spellchecking'. Try using the native package manager for Red Hat Enterprise
>> Linux () to install a package with similar name to 'enchant'.
>>
>> Error: Unable to prepare package AbiWord Word Processor.
>> ------------------------------------------------------------------------
>>
>> I downloaded and installed enchant (enchant-1.3.0.tar) but the above error
>> message persists. I don't know if I installed it using the "native package
>> manager" from the error message but I can now run enchant from the command line
>> so it looks like it installed correctly, i.e.
>
> If you downloaded a tarball and compiled it yourself (as implied by your
> mention of enchant .tar) then one could say you didn't use a package at
> all. In the case of RedHat the package type would be the RedHat Package
> Management, aka RPM so if you can find a recent RPM for enchant that is
> more likely to get properly registered and picked up correctly. It may
> also be possible to correctly install enchant the other way but using the
> RPMs provided is your best bet.
>
>> Any ideas?
>
> Do let us know if you manage to sort this out yourself in the meantime but
> someone else might be able to provide better advice but you will have to
> wait and hope.
>
> --
> Alan
>
>
-----------------------------------------------
To unsubscribe from this list, send a message to
abiword-user-request@abisource.com with the word
unsubscribe in the message body.
Received on Thu Feb 8 21:00:45 2007