Apache OpenOffice (AOO) Bugzilla – Full Text Issue Listing |
Summary: | OpenBSD porting: regcomp cannot find some java libraries because of "non-standard" path | ||||||
---|---|---|---|---|---|---|---|
Product: | porting | Reporter: | robert | ||||
Component: | code | Assignee: | AOO issues mailing list <issues> | ||||
Status: | ACCEPTED --- | QA Contact: | |||||
Severity: | Trivial | ||||||
Priority: | P3 | CC: | issues | ||||
Version: | OOO320m12 | ||||||
Target Milestone: | 4.x | ||||||
Hardware: | All | ||||||
OS: | Other OS | ||||||
Issue Type: | DEFECT | Latest Confirmation in: | --- | ||||
Developer Difficulty: | --- | ||||||
Attachments: |
|
Description
robert
2010-02-12 17:57:47 UTC
Created attachment 67791 [details]
unx.mk
Ok that's not even enough because then packaging will fail because of the same issue, so it has to be set in the environment itself. In an OOo installation set, openoffice.org/ure/bin/regcomp is a shell script that calls javaldx to extend LD_LIBRARY_PATH (because various JVMs have internal issues where a plain dlopen(libjvm.so) will lead to a VM where some part like AWT do not work) and only then calls the true regcomp.bin binary. In the build environment, however, regcomp is not the shell script but a duplication of regcomp.bin. I assume that the problems with the JVM on OpenBSD are such that javaldx setting LD_LIBRARY_PATH would work around them, and I assume that the problems you report are in a call to regcomp. Therefore, I would suggest to change cpputools to deliver the appropriate shell script as regcomp (and change all the calls to regcomp from within the build environment to tell javaldx to use the correct JVM, -env:UNO_JAVA_JFW_ENV_JREHOME=true -env:UNO_JAVA_JFW_ENV_CLASSPATH=true). . Reset assigne to the default "issues@openoffice.apache.org". |