You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello,
Quick run-down of my setup in case that becomes relevant I'm running:
64 bit Ubuntu 14.04 with an i7-4510U
I have the 32 bit version of eclipse.
While following the tutorial, I came across the error: "BWMirror API supports only x86 architecture." The FAQ states that it's because I don't have the 32 bit version of the jre installed. That was originally true, but I have since installed the 32 bit version, pointed eclipse to it as suggested. The problem persists, even after un-installing the 64bit jre, and setting the run configuration to include "-d32" which causes no issues(-d64 gives : "Error: This Java instance does not support a 64-bit JVM."). So I'm fairly confident that I am using the 32bit version of the jre. I went and found the section of code that is checking the version:
String arch = System.getProperty("os.arch");
String dllNames[] = {"bwapi_bridge" + VERSION, "libgmp-10", "libmpfr-4"};
if(!arch.equals("x86")){
throw new UnsupportedOperationException("BWMirror API supports only x86 architecture.");
}
When printing System.getProperty("os.arch"); on my system and it prints out "i386". This explains why it's throwing the error. However when looking at the Configuration tab from (Help->About Eclipse-> Installation Details) there is some potentially relevant information:
__wbp.linux.disableScreenshotWorkarounds=false
applicationXMI=org.eclipse.ui.workbench/LegacyIDE.e4xmi
awt.toolkit=sun.awt.X11.XToolkit
eclipse.application=org.eclipse.ui.ide.workbench
eclipse.buildId=4.5.2.M20160212-1500
eclipse.commands=-os
linux
-ws
gtk
-arch
x86
Specifically it lists -arch with x86 when printing System.getProperty("os.arch") is giving me i386. I'm not sure if there is something wrong with my installation or if the check for the os.arch needs to be more general.
Update: An odd work around I came up with was adding the below code in main.
System.setProperty("os.arch", "x86");
However that just lead to a new error which I'll post here because I'm not sure if it's relevant.
Exception in thread "main" java.lang.UnsatisfiedLinkError: no bwapi_bridge2_5 in java.library.path
at java.lang.ClassLoader.loadLibrary(Unknown Source)
at java.lang.Runtime.loadLibrary0(Unknown Source)
at java.lang.System.loadLibrary(Unknown Source)
at bwapi.Mirror.<clinit>(Mirror.java:92)
at TestBot1.<init>(TestBot1.java:7)
at TestBot1.main(TestBot1.java:89)
The text was updated successfully, but these errors were encountered:
Hello,
Quick run-down of my setup in case that becomes relevant I'm running:
64 bit Ubuntu 14.04 with an i7-4510U
I have the 32 bit version of eclipse.
While following the tutorial, I came across the error: "BWMirror API supports only x86 architecture." The FAQ states that it's because I don't have the 32 bit version of the jre installed. That was originally true, but I have since installed the 32 bit version, pointed eclipse to it as suggested. The problem persists, even after un-installing the 64bit jre, and setting the run configuration to include "-d32" which causes no issues(-d64 gives : "Error: This Java instance does not support a 64-bit JVM."). So I'm fairly confident that I am using the 32bit version of the jre. I went and found the section of code that is checking the version:
When printing System.getProperty("os.arch"); on my system and it prints out "i386". This explains why it's throwing the error. However when looking at the Configuration tab from (Help->About Eclipse-> Installation Details) there is some potentially relevant information:
Specifically it lists -arch with x86 when printing System.getProperty("os.arch") is giving me i386. I'm not sure if there is something wrong with my installation or if the check for the os.arch needs to be more general.
Update: An odd work around I came up with was adding the below code in main.
However that just lead to a new error which I'll post here because I'm not sure if it's relevant.
The text was updated successfully, but these errors were encountered: