Issue 1530 - liblexps638li.so component was unable to be registered
Summary: liblexps638li.so component was unable to be registered
Status: CLOSED DUPLICATE of issue 1218
Alias: None
Product: Installation
Classification: Application
Component: code (show other issues)
Version: 638
Hardware: PC Linux, all
: P3 Trivial (vote)
Target Milestone: ---
Assignee: Olaf Felka
QA Contact: issues@installation
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2001-08-25 19:59 UTC by nevend
Modified: 2003-09-08 16:53 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description nevend 2001-08-25 19:59:48 UTC 
During the installation of the new built 638 I got an error 
'liblexps638li.so component was unable to be registered'
I hit 'Ignore' and the installation completed. I am not sure what is that 
component for and if this is fatal.
I am using Red Hat 7.1 on a i686 and 256MB RAM.
Comment 1 Olaf Felka 2001-08-27 08:56:22 UTC 
Bouble

*** This issue has been marked as a duplicate of 1218 ***
Comment 2 Olaf Felka 2001-08-27 08:57:04 UTC 
Not bouble => DOUBLE!! :-)
Comment 3 khendricks 2001-08-27 20:19:03 UTC 
Hi,
That library is the library that interfaces with the spellchecking 
software aspell and pspell.

So in order to register that library, regcomp must be able to find 
libpspell.so and any all libraries it requires.

libpspell.so requires libstdc++

The registration is failing (probably) because it can not find the 
right libstdc++ on your system.

Here is a trcik you can do to solve this issue:

cd OpenOffice638/program
export LD_LIBRARY_PATH=`pwd`
ldd libexps638li.so
ldd libpspell.so

And make sure that ldd can find all of the proper libraries.  My 
guess is it will not find the libstdc++ one (it has been renamed 
under some linux releases).

If that is the case simply create a simlink with a new new to your 
own version of libstdc++ and everything should start working 
once you re-install openoffice.

Hope this helps,

Kevin

ps: this failure should not be fatal to running openoffice as long 
as you don't use spellchecking  but others have reported that 
creating the symlink from your libstdc++ to the name used on the 
original OO build system does help stability.