Summary: | app-eselect/eselect-java-0.1.0 - run-java-tool.bash filename breaks BlackBerry 10 Simulator installer | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Dennis Schridde <dschridde+gentoobugs> |
Component: | [OLD] Java | Assignee: | Java team <java> |
Status: | RESOLVED OBSOLETE | ||
Severity: | normal | CC: | gentoo |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Dennis Schridde
2015-06-16 00:39:37 UTC
The same think hits us later, at: resolveLink "$actvm" actvm="$resolvedLink" I understand, that run-java-tool.bash needs the name of $0 to dispatch properly, which means that resolving the link will break it. Thus I currently have no suggestion how to fix this correctly. This sounds pretty dumb. I don't know how resolving the symlink and checking the result is supposed to give any indication that it is a working VM or not. I haven't looked at it but as a workaround, you might be able to run it with PATH=$(java-config -O)/bin:${PATH}. I don't think that will work, as it always resolves the symlink of "java", after searching all dirs in $PATH for it. But I found another workaround: Running the installer as "./the-installer.bin LAX_VM java" forces the JVM binary to be "java", which makes the symlink resolver fail, so it uses the name directly. Please note that starting it as "./the-installer.bin LAX_VM /usr/bin/java" will not work, as then it will still resolve the symlink of the forced binary. old version 'app-eselect/eselect-java-0.1.0' is gone. closing. |