|
Apache OpenOffice (AOO) Bugzilla – Full Text Issue Listing |
| Summary: | Errors found while building in debug mode | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Installation | Reporter: | bejgumsatish <satish.201283> | ||||
| Component: | code | Assignee: | AOO issues mailing list <issues> | ||||
| Status: | CLOSED OBSOLETE | QA Contact: | |||||
| Severity: | Trivial | ||||||
| Priority: | P3 | CC: | issues, knmc, oooforum, pavel | ||||
| Version: | 680m233 | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | PC (x86_64) | ||||||
| OS: | Linux, all | ||||||
| Issue Type: | DEFECT | Latest Confirmation in: | --- | ||||
| Developer Difficulty: | --- | ||||||
| Attachments: |
|
||||||
|
Description
bejgumsatish
2007-10-19 06:03:02 UTC
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 |