Opened 13 years ago
Closed 8 years ago
#9839 closed defect (obsolete)
problem to build vboxjxpcom.jar
Reported by: | brandon head | Owned by: | |
---|---|---|---|
Component: | other | Version: | VirtualBox 4.1.4 |
Keywords: | Cc: | ||
Guest type: | other | Host type: | other |
Description (last modified by )
There are errors to build vboxjxpcom.jar with "kmk VBOX_WITH_JMSCOM=1" It looks like making the glue layer does not work correctly. Below are the errors which starts missing method encodeBase64()
/root/a/VirtualBox-4.1.4_OSE/out/linux.amd64/release/obj/vboxjmscom-gen/jmscomgen/java/IGuest.java:266: cannot find symbol symbol : method encodeBase64(byte[]) location: class org.virtualbox_4_1.mscom.Helper
retVal = Helper.invoke(getTypedWrapped(), "setProcessInput" , new Variant(pid), new Variant(flags), new Variant(timeoutMS), Helper.encodeBase64(data));
/root/a/VirtualBox-4.1.4_OSE/out/linux.amd64/release/obj/vboxjmscom-gen/jmscomgen/java/IMachineDebugger.java:287: cannot find symbol symbol : method encodeBase64(byte[]) location: class org.virtualbox_4_1.mscom.Helper
Helper.invoke(getTypedWrapped(), "writePhysicalMemory" , new Variant(address.longValue()), new Variant(size), Helper.encodeBase64(bytes));
/root/a/VirtualBox-4.1.4_OSE/out/linux.amd64/release/obj/vboxjmscom-gen/jmscomgen/java/IMachineDebugger.java:303: cannot find symbol symbol : method encodeBase64(byte[]) location: class org.virtualbox_4_1.mscom.Helper
Helper.invoke(getTypedWrapped(), "writeVirtualMemory" , new Variant(cpuId), new Variant(address.longValue()), new Variant(size), Helper.encodeBase64(bytes));
Note: Some input files use or override a deprecated API. Note: Recompile with -Xlint:deprecation for details. 3 errors 2 warnings kmk: * root/a/VirtualBox-4.1.4_OSE/out/linux.amd64/release/obj/VBoxJMscom-inst-jar/vboxjmscom.jar Error 1 kmk: * Waiting for unfinished jobs.... kBuild: Linking vboxjxpcom.jar kmk: * Exiting with status 2
Change History (2)
comment:1 by , 12 years ago
Description: | modified (diff) |
---|
comment:2 by , 8 years ago
Resolution: | → obsolete |
---|---|
Status: | new → closed |
Please reopen if still relevant with a recent VirtualBox release.
There is a reason why this switch is disabled by default ...