Issue 82773 - Errors found while building in debug mode
Summary: Errors found while building in debug mode
Status: ACCEPTED
Alias: None
Product: Installation
Classification: Application
Component: code (show other issues)
Version: 680m233
Hardware: PC (x86_64) Linux, all
: P3 Trivial with 1 vote (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-10-19 06:03 UTC by bejgumsatish
Modified: 2013-02-07 21:54 UTC (History)
2 users (show)

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


Attachments
Log file in instsetoo_native/unxlngi6/OpenOffice/native/install/log/ (1.33 MB, text/plain)
2007-10-19 06:12 UTC, bejgumsatish
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description bejgumsatish 2007-10-19 06:03:02 UTC
ERROR: The following errors occured in packaging process:

Thread:      1 :Error osl_getAsciiFunctionSymbol:
/work/savesets/satish/SRC680_m233/solver/680/unxlngi6/lib/bootstrap.uno.so:
undefined symbol: component_getImplementationEnvironmentExt
Thread:      1 :Error osl_getAsciiFunctionSymbol:
/work/savesets/satish/SRC680_m233/solver/680/unxlngi6/lib/bootstrap.uno.so:
undefined symbol: component_getImplementationEnvironmentExt
Thread:      1 :Error osl_getAsciiFunctionSymbol:
/work/savesets/satish/SRC680_m233/solver/680/unxlngi6/lib/bootstrap.uno.so:
undefined symbol: component_getImplementationEnvironmentExt
Thread:      1 :Error osl_getAsciiFunctionSymbol:
/work/savesets/satish/SRC680_m233/solver/680/unxlngi6/lib/bootstrap.uno.so:
undefined symbol: component_getImplementationEnvironmentExt
Thread:      1 :Error osl_getAsciiFunctionSymbol:
/work/savesets/satish/SRC680_m233/solver/680/unxlngi6/lib/bootstrap.uno.so:
undefined symbol: component_getImplementationEnvironmentExt
Thread:      1 :Error osl_getAsciiFunctionSymbol:
/work/savesets/satish/SRC680_m233/solver/680/unxlngi6/lib/bootstrap.uno.so:
undefined symbol: component_getImplementationEnvironmentExt
Thread:      1 :Error osl_getAsciiFunctionSymbol:
/work/savesets/satish/SRC680_m233/solver/680/unxlngi6/lib/bootstrap.uno.so:
undefined symbol: component_getImplementationEnvironmentExt
Thread:      1 :Error osl_getAsciiFunctionSymbol:
/work/savesets/satish/SRC680_m233/solver/680/unxlngi6/lib/bootstrap.uno.so:
undefined symbol: component_getImplementationEnvironmentExt
Thread:      1 :Error osl_getAsciiFunctionSymbol:
/work/savesets/satish/SRC680_m233/solver/680/unxlngi6/lib/bootstrap.uno.so:
undefined symbol: component_getImplementationEnvironmentExt
Thread:      1 :Error osl_getAsciiFunctionSymbol: libunsafe_uno_uno.so:
undefined symbol: component_canUnload
Thread:      1 :Error osl_getAsciiFunctionSymbol: libunsafe_uno_uno.so:
undefined symbol: component_canUnload
Thread:      1 :Error osl_getAsciiFunctionSymbol: libunsafe_uno_uno.so:
undefined symbol: component_canUnload
Thread:      1 :Error osl_getAsciiFunctionSymbol: acceptor.uno.so: undefined
symbol: component_getImplementationEnvironmentExt
Thread:      1 :Error osl_getAsciiFunctionSymbol:
/work/savesets/satish/SRC680_m233/solver/680/unxlngi6/lib/bootstrap.uno.so:
undefined symbol: component_getImplementationEnvironmentExt
Thread:      1 :Error osl_getAsciiFunctionSymbol: bridgefac.uno.so: undefined
symbol: component_getImplementationEnvironmentExt
Thread:      1 :Error osl_getAsciiFunctionSymbol: connector.uno.so: undefined
symbol: component_getImplementationEnvironmentExt
Thread:      1 :Error osl_getAsciiFunctionSymbol: introspection.uno.so:
undefined symbol: component_getImplementationEnvironmentExt
Thread:      1 :Error osl_getAsciiFunctionSymbol: invocadapt.uno.so: undefined
symbol: component_getImplementationEnvironmentExt
Thread:      1 :Error osl_getAsciiFunctionSymbol: invocation.uno.so: undefined
symbol: component_getImplementationEnvironmentExt
Thread:      1 :Error osl_getAsciiFunctionSymbol: javaloader.uno.so: undefined
symbol: component_getImplementationEnvironmentExt
Thread:      1 :Error osl_getAsciiFunctionSymbol: javavm.uno.so: undefined
symbol: component_getImplementationEnvironmentExt
Thread:      1 :Error osl_getAsciiFunctionSymbol: namingservice.uno.so:
undefined symbol: component_getImplementationEnvironmentExt
Thread:      1 :Error osl_getAsciiFunctionSymbol: proxyfac.uno.so: undefined
symbol: component_getImplementationEnvironmentExt
Thread:      1 :Error osl_getAsciiFunctionSymbol: reflection.uno.so: undefined
symbol: component_getImplementationEnvironmentExt
Thread:      1 :Error osl_getAsciiFunctionSymbol: remotebridge.uno.so: undefined
symbol: component_getImplementationEnvironmentExt
Thread:      1 :Error osl_getAsciiFunctionSymbol: stocservices.uno.so: undefined
symbol: component_getImplementationEnvironmentExt
Thread:      1 :Error osl_getAsciiFunctionSymbol: streams.uno.so: undefined
symbol: component_getImplementationEnvironmentExtThread:      1 :Error
osl_getAsciiFunctionSymbol: textinstream.uno.so: undefined symbol:
component_getImplementationEnvironmentExt
Thread:      1 :Error osl_getAsciiFunctionSymbol: textoutstream.uno.so:
undefined symbol: component_getImplementationEnvironmentExt
Thread:      1 :Error osl_getAsciiFunctionSymbol: uuresolver.uno.so: undefined
symbol: component_getImplementationEnvironmentExt
*********************************************************************
Comment 1 bejgumsatish 2007-10-19 06:12:03 UTC
Created attachment 49021 [details]
Log file in instsetoo_native/unxlngi6/OpenOffice/native/install/log/
Comment 2 Olaf Felka 2007-10-19 06:51:25 UTC
Please have a look.
Comment 3 bejgumsatish 2007-10-22 06:24:34 UTC
Please any help in this regard 
I can start Open Office but with some errors
thanks in advance
Comment 4 saperski 2008-04-11 11:42:50 UTC
Those messages appear because getLibEnv() probes first for the
"component_getImplementationEnvironmentExt" and, if it's not found, continues
with "component_getImplementationEnvironment"

It seems that the former is defined only by the test component from the
udk/cppuhelper/test/testcmp directory.

The test component itself does not really build, but maybe this could be fixed.

We can either:

1) remove any attempt to load component_getImplementationEnvironmentExt
2) make osl less noisy
3) ask installer to ignore OSL_TRACE messages

I think that #3 is the best fix.

References:
http://lxr.go-oo.org/source/udk/cppuhelper/source/shlib.cxx#297
getLibEnv()

http://lxr.go-oo.org/source/porting/sal/osl/unx/module.c#220
osl_getAsciiFunctionSymbol()

http://lxr.go-oo.org/source/udk/cppuhelper/test/testcmp/TestComponent.cxx#222
Comment 5 jens-heiner.rechtien 2008-04-11 13:35:45 UTC
@kr: reassign
Comment 6 kay.ramme 2008-04-11 14:31:45 UTC
Do I understand correctly, that this is "ugly" only, but does not break any
functionality?

Anyway, dumping some log output because a function failed which return result is
to be handled in the calling function is stupid at best. So, this kind of fits
to OOo error handling approach ... ;-)

Two solutions:
-1- Remove the logging from "osl_getAsciiFunctionSymbol".
-2- Change the query order, shlib.cxx. 

Obviously, -1- would be the right thing to do, but I fear that others would hit
me for that, as this is their approach for finding problems ... let's see.
Approach -2- would cure the current situation and may be revised later on, when
most components implement "component_getImplementationEnvironmentExt" ...

So, let's go ...