Azureus x86_64: Any Luck?
I’ve been trying to fiddle with the latest version of Azureus for AMD64 to no avail. Check out the code:
[mike@tek1024 azureus]$ ./azureus
Starting Azureus...
Java exec found in PATH. Verifying...
Suitable java version found [java = 1.5.0_06]
Configuring environment...
Loading Azureus:
java -Xms16m -Xmx128m -cp "/home/mike/download/azureus/Azureus2.jar:/home/mike/download/azureus/swt.jar" -Djava.library.path="/home/mike/download/azureus" -Dazureus.install.path="/home/mike/download/azureus" org.gudy.azureus2.ui.swt.Main ''Exception in thread "main" java.lang.UnsatisfiedLinkError: /home/mike/download/azureus/libswt-pi-gtk-3139.so: /home/mike/download/azureus/libswt-pi-gtk-3139.so: cannot open shared object file: No such file or directory
at java.lang.ClassLoader$NativeLibrary.load(Native Method)
at java.lang.ClassLoader.loadLibrary0(Unknown Source)
at java.lang.ClassLoader.loadLibrary(Unknown Source)
at java.lang.Runtime.loadLibrary0(Unknown Source)
at java.lang.System.loadLibrary(Unknown Source)
at org.eclipse.swt.internal.Library.loadLibrary(Library.java:123)
at org.eclipse.swt.internal.gtk.OS.
at org.eclipse.swt.internal.Converter.wcsToMbcs(Converter.java:63)
at org.eclipse.swt.internal.Converter.wcsToMbcs(Converter.java:54)
at org.eclipse.swt.widgets.Display.
at org.gudy.azureus2.ui.swt.mainwindow.SWTThread.
at org.gudy.azureus2.ui.swt.mainwindow.SWTThread.createInstance(SWTThread.java:58)
at org.gudy.azureus2.ui.swt.mainwindow.Initializer.
at org.gudy.azureus2.ui.swt.Main.
at org.gudy.azureus2.ui.swt.Main.main(Main.java:142)
Azureus TERMINATED.
Having downloaded the latest SWT for 64 bit GTK windowing didn’t help either. Finally broke down to use the plain old x86, 32-bit version and it worked flawlessly. What gives?
3 Responses to “Azureus x86_64: Any Luck?”
-
Mr. W Says:
December 28th, 2005 at 21:34:02This is a bit off topic, but you have a new 64 processor, right? That’s hot. I want to get one. Le sigh
-
Mr. W Says:
January 1st, 2006 at 02:07:55btw, no advice from me
-
Brian Lee Says:
January 2nd, 2006 at 00:56:16Try using the default java installation that came with your distro. .
-
Mike Says:
January 10th, 2006 at 04:00:57I tried that, but for FC4 x86_64, it’s gij, and that was throwing all sorts of errors (which is why I started trying to dink around with any of this in the first place). Could be a hardware-config anomaly on my end.
-
Werner Flamme Says:
January 24th, 2006 at 07:33:31Mh, just googling to find a solution. Brandnew x86_64, installed SuSE 10.0, Java 1.4.2, and exacly the same error.
All files there, all flagged 777, no avail.On www.redhat.com/archives/fedora-devel-java-list/2006-January/msg00067.html I found “I guess it won’t run on x86_64 due to the threading issue that isn’t fixed yet.” Great
-
darkfrog Says:
March 10th, 2006 at 21:29:30Okay, for anyone else that stumbles here looking for a solution to the problem. I realized it while I was looking at this page. I accidentally installed the i386 version of the JDK on my 64-bit machine instead of the special 64-bit edition of the JDK. Make sure you have that 64-bit JRE and it should run just fine.
-
bforbes Says:
April 2nd, 2006 at 05:17:15Okay, for anyone else that stumbles here looking for a solution to the problem. I realized it while I was looking at this page. I accidentally installed the i386 version of the JDK on my 64-bit machine instead of the special 64-bit edition of the JDK. Make sure you have that 64-bit JRE and it should run just fine.
This also worked for me.
December 28th, 2005 at 21:34:02
This is a bit off topic, but you have a new 64 processor, right? That’s hot. I want to get one. Le sigh
January 1st, 2006 at 02:07:55
btw, no advice from me
January 2nd, 2006 at 00:56:16
Try using the default java installation that came with your distro. .
January 10th, 2006 at 04:00:57
I tried that, but for FC4 x86_64, it’s gij, and that was throwing all sorts of errors (which is why I started trying to dink around with any of this in the first place). Could be a hardware-config anomaly on my end.
January 24th, 2006 at 07:33:31
Mh, just googling to find a solution. Brandnew x86_64, installed SuSE 10.0, Java 1.4.2, and exacly the same error.
All files there, all flagged 777, no avail.
On www.redhat.com/archives/fedora-devel-java-list/2006-January/msg00067.html I found “I guess it won’t run on x86_64 due to the threading issue that isn’t fixed yet.” Great
March 10th, 2006 at 21:29:30
Okay, for anyone else that stumbles here looking for a solution to the problem. I realized it while I was looking at this page. I accidentally installed the i386 version of the JDK on my 64-bit machine instead of the special 64-bit edition of the JDK. Make sure you have that 64-bit JRE and it should run just fine.
April 2nd, 2006 at 05:17:15
Okay, for anyone else that stumbles here looking for a solution to the problem. I realized it while I was looking at this page. I accidentally installed the i386 version of the JDK on my 64-bit machine instead of the special 64-bit edition of the JDK. Make sure you have that 64-bit JRE and it should run just fine.
This also worked for me.