Apache OpenOffice (AOO) Bugzilla – Issue 82773
Errors found while building in debug mode
Last modified: 2024-02-18 03:03:26 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 *********************************************************************
Created attachment 49021 [details] Log file in instsetoo_native/unxlngi6/OpenOffice/native/install/log/
Please have a look.
Please any help in this regard I can start Open Office but with some errors thanks in advance
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
@kr: reassign
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 ...
Obsolete build