Use new java build system.
Created attachment 90984 [details, diff] openoffice-2.0.3.ebuild.diff Simple patch... But will allow compiling using jdk1.5 again.
Created attachment 90986 [details, diff] openoffice-2.0.3.ebuild.diff
I just want to know if the following error is related to this thread (as it would take over 20 hours to recompile with this patch): ------------------------------------------------------------------------------------------------------------------ register component 'uriproc.uno.so' in registry 'uno_services.rdb' succesful! register component 'constructors.uno.so' in registry 'uno_services.rdb' succesful! regcomp -register -br ../../unxlngppc.pro/lib/uno_types.rdb -r ../../unxlngppc.pro/lib/uno_services.rdb \ -c javaloader.uno.so -c javavm.uno.so register component 'javaloader.uno.so' in registry '../../unxlngppc.pro/lib/uno_services.rdb' succesful! register component 'javavm.uno.so' in registry '../../unxlngppc.pro/lib/uno_services.rdb' succesful! regcomp -register -br ../../unxlngppc.pro/misc/bridgetest/bootstrap.rdb -r ../../unxlngppc.pro/lib/uno_services.rdb -c \ file:///var/tmp/portage/openoffice-2.0.3/work/ooo-build-ooc680-m7/build/ooc680-m7/testtools/source/bridgetest/../../unxlngppc.pro/class/testComponent.jar \ -env:URE_INTERNAL_JAVA_DIR=file:///var/tmp/portage/openoffice-2.0.3/work/ooo-build-ooc680-m7/build/ooc680-m7/solver/680/unxlngppc.pro/bin [Java framework]sunjavaplugin.so could not load Java runtime library: file:///opt/ibm-jdk-bin-1.4.2.5/jre/bin/classic/libjvm.so.register component 'file:///var/tmp/portage/openoffice-2.0.3/work/ooo-build-ooc680-m7/build/ooc680-m7/testtools/source/bridgetest/../../unxlngppc.pro/class/testComponent.jar' in registry '../../unxlngppc.pro/lib/uno_services.rdb' failed! error (CannotRegisterImplementationException): Could not create Java implementation loader using loader com.sun.star.loader.Java2 dmake: Error code 1, while making '../../unxlngppc.pro/lib/uno_services.rdb' dmake: '../../unxlngppc.pro/lib/uno_services.rdb' removed. '---* tg_merge.mk *---' ERROR: Error 65280 occurred while making /var/tmp/portage/openoffice-2.0.3/work/ooo-build-ooc680-m7/build/ooc680-m7/testtools/source/bridgetest make: *** [stamp/build] Fehler 1 !!! ERROR: app-office/openoffice-2.0.3 failed. ------------------------------------------------------------------------------------------------------------------ I'm using ibm-jdk-bin-1.4.2.5 for generation 1 java system and ibm-jdk-bin-1.5.0-r11 as generation 2.
hmm, sorry my error seems to be more related to #126777 but I'm on ppc and I'm not using any fancy CFLAGS. #126777 is closed... should I reopen it?
@Christoph You hit the same problem as in comment 12 from bug 135249. https://bugs.gentoo.org/show_bug.cgi?id=135249#c12 As far as I understand it a variation of this patch could solve it. http://go-oo.org/patches/64bit/64bit-jdk-server-paths.diff Please open a new bugreport. When I got OOo source around I check for a proper patch.
*** Bug 140080 has been marked as a duplicate of this bug. ***
Created attachment 91682 [details, diff] openoffice-2.0.3.ebuild.diff
This worked fine for me with Sun JDK 1.5. I ran oowriter and used the "help" feature with no problem.
@Alon: I'm really not firm with the new java-build system, so my question is: Will this still allow people with java-1.4 to build?
Adding java-herd for advice: What would be right thing to do here, if we want the package to be buildable with both java-1.4 and 1.5 (and also have it to work on stable plattforms)?
(In reply to comment #9) > @Alon: I'm really not firm with the new java-build system, so my question is: > Will this still allow people with java-1.4 to build? Yes. The new build system alter the -source and -target parameters of the compiler in order to compile stuff that had not compiled under jdk 1.5. It will allow the unmask of jdk 1.5 in portage without patching all incompatible packages. By default, it compiles using a pre-selected compiler specified at /etc/java-config-2. I, personally, do not agree with this approach, and think that incompatible packages should be patched and send to upstream to inclusion. Dragging the incompatible packages throughout java evolution is not wise. But this is the approach the java-herd selected.
(In reply to comment #11) > > Yes. > The new build system alter the -source and -target parameters of the compiler > in order to compile stuff that had not compiled under jdk 1.5. > It will allow the unmask of jdk 1.5 in portage without patching all > incompatible packages. By default, it compiles using a pre-selected compiler > specified at /etc/java-config-2. Actually OOo does build fine with jdk-1.5 out-of-the-box, so does this change anything here? Should we use java-pkg-2 instead?
(In reply to comment #12) > Actually OOo does build fine with jdk-1.5 out-of-the-box, I know!!! But noone can now compile OOo with jdk-1.5 since the 1.5 was removed from the old java system... In order to use jdk-1.5 you MUST switch into the new build system. > so does this change > anything here? Should we use java-pkg-2 instead? Yes. All you need to do is to switch into the new build system inherit java-pkg-opt-2 and use java-pkg-opt-2_pkg_setup as in attachment#91682 [details, diff].
(In reply to comment #13) > (In reply to comment #12) > > Actually OOo does build fine with jdk-1.5 out-of-the-box, > > I know!!! > But noone can now compile OOo with jdk-1.5 since the 1.5 was removed from the > old java system... In order to use jdk-1.5 you MUST switch into the new build > system. > > > so does this change > > anything here? Should we use java-pkg-2 instead? > > Yes. > All you need to do is to switch into the new build system inherit > java-pkg-opt-2 and use java-pkg-opt-2_pkg_setup as in attachment#91682 [details, diff] [edit]. > java-pkg-2 is a different thing than java-pkg-opt-2, the first is what I asked about..
(In reply to comment #14) > java-pkg-2 is a different thing than java-pkg-opt-2, the first is what I asked > about.. I know... you need java-pkg-opt-2 and not java-pkg-2 since you use java for subcomponents and not build a full java application. From http://www.gentoo.org/proj/en/java/java-devel.xml: > java-pkg-2.eclass Any and all java based packages > java-pkg-opt-2.eclass Package that have optional java support
(In reply to comment #15) > > I know... you need java-pkg-opt-2 and not java-pkg-2 since you use java for > subcomponents and not build a full java application. > > From http://www.gentoo.org/proj/en/java/java-devel.xml: > > java-pkg-2.eclass Any and all java based packages > > java-pkg-opt-2.eclass Package that have optional java support > Thanks, found that in the meantime, should wait a little bit longer before posting ;) Anyway, if I'm correct we can't add this to the current 2.0.3-ebuild as this is already stable and we would need unstable stuff like java-config-2 for this. So this will have to wait for 2.0.4. As this should be coming soonish, I don't want to add a rev-bump for 2.0.3 which would force all unstable users through anoter long recompile.
Done this in 2.0.4_rc1, closing this bug
I think java-pkg-opt-2_pkg_setup is missing from pkg_setup
Created attachment 97034 [details, diff] openoffice-2.0.4_rc1-r1.ebuild.diff
(In reply to comment #18) > I think java-pkg-opt-2_pkg_setup is missing from pkg_setup > This is not necessary, java-pkg-opt-2_pkg_setup is autmatically called by the eclass
