Issue 3652 - setup.bin: error loading libvos2GCC.so
Summary: setup.bin: error loading libvos2GCC.so
Status: CLOSED FIXED
Alias: None
Product: Build Tools
Classification: Code
Component: code (show other issues)
Version: 641
Hardware: PC Linux, all
: P3 Trivial (vote)
Target Milestone: ---
Assignee: Unknown
QA Contact: issues@tools
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-03-25 14:56 UTC by chris
Modified: 2003-02-24 14:02 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 chris 2002-03-25 14:56:57 UTC 
I built OOO_STABLE_1 from March 25 on Debian unstable using GCC 2.95. On trying
to run setup, I get the error message:

setup:/tmp/sv005.tmp/setup.bin: error while loading shared libraries:
libvos2GCC.so: cannot open shared object file: No such file or directory

On IRC I was told:

<@reals> its sort of know problem, the solution isn't known yet. it expects gcc3
specific files, so changes to scp (preferably ones that allow both to happen)
are needed
Comment 1 hcstudt 2002-04-22 21:30:52 UTC 
I have the same problem.

Date: Sun, 21 Apr 2002 20:10:23 +0200
From: Hans Christian Studt <hcstudt@post10.tele.dk>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0rc1)
Gecko/20020417
X-Accept-Language: en-us, en
MIME-Version: 1.0
To:  dev@openoffice.org
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [dev] 641d setup problem

After a complete build og 641d I get this error when running the setup
program.

------------- OUTPUT --------------
(oo_641d_src/instsetoo/unxlngi3.pro/01/normal) #./setup
glibc version: 2.2.4
/tmp/sv002.tmp/setup.bin: error while loading shared libraries:
libvos2GCC.so: cannot open shared object file: No such file or directory
------------------------------------------

What could be the problem ?

Regards
Hans Christian Studt
Comment 2 chris 2002-05-07 16:07:46 UTC 
Since we have been building with GCC 3.0.x, we no longer have this
problem.  Hans Christian told me it is no longer a problem for him
either.  Closing this issue.
Comment 3 chris 2003-02-24 14:02:42 UTC 
Closing old issue