Summary: | openoffice-2.0.1 wont compile through "ebuild openoffice compile" with use-flag java enabled | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Philipp Reinkemeier <philipp.reinkemeier> |
Component: | New packages | Assignee: | Gentoo Office Team <office> |
Status: | VERIFIED INVALID | ||
Severity: | normal | CC: | gentoo-bugs, philipp.reinkemeier |
Priority: | Low | ||
Version: | 2005.1 | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Philipp Reinkemeier
2006-01-23 14:40:17 UTC
*** This bug has been marked as a duplicate of 119577 *** Tested it again. It seems, that you can emerge it through command "emerge openoffice", but not through "ebuild /usr/portage/app-office/openoffice/openoffice-2.0.1.ebuild", which i used because i interrupted the emerge last night because of my noisy fan and continued it with the same command. So finally with "ebuild" it interrupts, with "emerge" not! May be, that there are some environment variables set in the ebuild, but outside the src_compile() function and therefore the "ebuild" command alone does not work. (In reply to comment #2) > > May be, that there are some environment variables set in the ebuild, but > outside the src_compile() function and therefore the "ebuild" command alone > does not work. > Yes and that is perfectly fine. Just to add to that: There are no relevant stuff vars set outside of src_compile() (only LINGUAS, but that doesn't count), anyway the problem seems to have been a messed up JAVA_HOME-var in your setup. But as it works when emerging the package properly, this is invalid I beg to differ, in src_unpack there is use amd64 && export DISTRO="Gentoo64" || export DISTRO="Gentoo" but it really should be in pkg_setup. Since we don't go through src_unpack with the ebuild command, the gentoo specific config file isn't used at all (as we dont have a DISTRO env var). That's where that strange java path is coming from (no broken $JAVA_HOME). >>the "ebuild" command alone >> does not work. >> >Yes and that is perfectly fine. Sorry, but bollocks. Particulary for an ebuild that's blocking openoffice-bin, how do you propose switching from openoffice-bin to native without 8 hours office downtime without "ebuild compile"? Anyway, if you just move this export where it belongs, ebuild compile works fine (fingers crossed, ask again in 8 hours if it really does...). Hm, sorry for flaming, it's late ;-). I missed comment #4 which puts comment #3 in perspective. (In reply to comment #5) > I beg to differ, in src_unpack there is > use amd64 && export DISTRO="Gentoo64" || export DISTRO="Gentoo" > but it really should be in pkg_setup. Since we don't go through src_unpack with > the ebuild command, the gentoo specific config file isn't used at all (as we > dont have a DISTRO env var). That's where that strange java path is coming from > (no broken $JAVA_HOME). You are right and wrong. ;) You are right that that this particular line belongs to src_compile (or pkg_setup), but you are wrong that this had anything to do with the original bug, otherwise the error message would have been totally different. Anyway, I've moved it up now, thanks for noting this (In reply to comment #7) > (In reply to comment #5) > > Since we don't go through src_unpack with > > the ebuild command, the gentoo specific config file isn't used at all (as we > > dont have a DISTRO env var). That's where that strange java path is coming from > > (no broken $JAVA_HOME). > > You are right and wrong. ;) > > You are right that that this particular line belongs to src_compile (or > pkg_setup), but you are wrong that this had anything to do with the original > bug, otherwise the error message would have been totally different. No, I'm right and right. :-D. I had the same bug message as the original reporter, after starting the ebuild command with DISTRO="Gentoo" ebuild foo compile it worked. Thats because without the DISTRO env variable the Gentoo specific config file you create in the ebuild doesn't get used and so the OOo build system falls back to the default dir for java, which is /usr/lib/SunJava2-1.4.2/bin/java Thats how I found the wrong line in the first place. > Anyway, I've moved it up now, thanks for noting this Thanks :-). You or the reporter could move this bug from INVALID to CLOSED. (In reply to comment #8) > I had the same bug message as the original > reporter, after starting the ebuild command with > DISTRO="Gentoo" ebuild foo compile > it worked. Thats because without the DISTRO env variable the Gentoo specific > config file you create in the ebuild doesn't get used and so the OOo build > system falls back to the default dir for java, which is > /usr/lib/SunJava2-1.4.2/bin/java I think this is feasible. Solution: > > Anyway, I've moved it up now, thanks for noting this > Thanks :-). > You or the reporter could move this bug from INVALID to CLOSED. > |