Summary: | subversion 1.1.0 emerge fails with java and jikes | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Jose Gonzalez Gomez <jgonzalez.openinput> |
Component: | Current packages | Assignee: | Paul de Vrieze (RETIRED) <pauldv> |
Status: | RESOLVED DUPLICATE | ||
Severity: | major | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Jose Gonzalez Gomez
2004-10-17 04:51:46 UTC
Sorry... it's evident that to reproduce the bug you must activate java support: ACCEPT_KEYWORDS="~x86" USE="java" emerge -vp subversion I missed the jikes use flag in the ebuild. Anyway, using -jikes didn't work, as the ebuild was incorrect. The following lines has missing quotes: if use java; then use jikes && myconf=${myconf} --with-jikes=yes use jikes || myconf=${myconf} --without-jikes fi I have added quotes to the myconf variable: if use java; then use jikes && myconf="${myconf} --with-jikes=yes" use jikes || myconf="${myconf} --without-jikes" fi After that, emerging this package with -jikes works as expected. Anyway, jikes support should be disabled until the bug in Subversion itself is fixed, as emerging the package with the jikes use flag causes the merge to fail. Prefixing the variables should not be necessary (because it _is_ a jikes bug). Please see http://subversion.tigris.org/issues/show_bug.cgi?id=2057 for more on this. Unless the javahl maintainer (whoever that is) speaks up on this, it's unlikely to get fixed. Not using jikes is IMHO the correct solution here, esp. considering that most people have the JDK anyway when they use Java-related packages. |