Bug 1557 : Unsatisfied Link Error running OPENGL on 64-bit ubuntu
Last modified: 2010-05-03 12:47




Status:
ASSIGNED
Resolution:
-
Priority:
P2
Severity:
normal

 

Reporter:
coldnebo
Assigned To:
fry

Attachment Type Created Size Actions

Description:   Opened: 2010-05-03 05:02
I'm running in the following env:

$ uname -a
Linux lkyrala-ibex-64 2.6.31-21-generic #59-Ubuntu SMP Wed Mar 24 07:28:27
UTC 2010 x86_64 GNU/Linux
$ lspci | grep VGA
01:00.0 VGA compatible controller: nVidia Corporation G84 [Quadro FX 370]
(rev a1)
$ nvidia-settings -q NvidiaDriverVersion
Attribute 'NvidiaDriverVersion' (lkyrala-ibex-64:0.0): 195.36.15


I get the following link error trying to run a sketch from either
Processing 1.1 or the generated application files under Ubuntu (I can
understand the generated app files perhaps being limited to 32bit, however
the Processing 1.1 app should run correctly with 64-bit OPENGL libraries):

Note: there is a related thread on the forums:
http://processing.org/discourse/yabb2/YaBB.pl?num=1271143980/3


processing.app.debug.RunnerException: UnsatisfiedLinkError:
/local/processing-1.1/libraries/opengl/library/libgluegen-rt.so:
/local/processing-1.1/libraries/opengl/library/libgluegen-rt.so: wrong ELF
class: ELFCLASS32 (Possible cause: architecture word width mismatch)
at processing.app.Sketch.placeException(Unknown Source)
at processing.app.debug.Runner.findException(Unknown Source)
at processing.app.debug.Runner.reportException(Unknown Source)
at processing.app.debug.Runner.exception(Unknown Source)
at processing.app.debug.EventThread.exceptionEvent(Unknown Source)
at processing.app.debug.EventThread.handleEvent(Unknown Source)
at processing.app.debug.EventThread.run(Unknown Source)
Exception in thread "Animation Thread" java.lang.UnsatisfiedLinkError:
/local/processing-1.1/libraries/opengl/library/libgluegen-rt.so:
/local/processing-1.1/libraries/opengl/library/libgluegen-rt.so: wrong ELF
class: ELFCLASS32 (Possible cause: architecture word width mismatch)
at java.lang.ClassLoader$NativeLibrary.load(Native Method)
at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:1803)
at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1728)
at java.lang.Runtime.loadLibrary0(Runtime.java:823)
at java.lang.System.loadLibrary(System.java:1028)
at
com.sun.gluegen.runtime.NativeLibLoader.loadLibraryInternal(NativeLibLoader.java:102)
at com.sun.gluegen.runtime.NativeLibLoader.access$000(NativeLibLoader.java:51)
at com.sun.gluegen.runtime.NativeLibLoader$1.run(NativeLibLoader.java:70)
at java.security.AccessController.doPrivileged(Native Method)
at
com.sun.gluegen.runtime.NativeLibLoader.loadGlueGenRT(NativeLibLoader.java:68)
at
com.sun.gluegen.runtime.NativeLibrary.ensureNativeLibLoaded(NativeLibrary.java:399)
at com.sun.gluegen.runtime.NativeLibrary.open(NativeLibrary.java:163)
at com.sun.gluegen.runtime.NativeLibrary.open(NativeLibrary.java:129)
at com.sun.opengl.impl.x11.DRIHack.begin(DRIHack.java:109)
at
com.sun.opengl.impl.x11.X11GLDrawableFactory.<clinit>(X11GLDrawableFactory.java:99)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:169)
at javax.media.opengl.GLDrawableFactory.getFactory(GLDrawableFactory.java:111)
at processing.opengl.PGraphicsOpenGL.allocate(Unknown Source)
at processing.core.PGraphics3D.setSize(Unknown Source)
at processing.core.PApplet.makeGraphics(Unknown Source)
at processing.core.PApplet.size(Unknown Source)
at processing.core.PApplet.size(Unknown Source)
at lightroom.setup(lightroom.java:45)
at processing.core.PApplet.handleDraw(Unknown Source)
at processing.core.PApplet.run(Unknown Source)
at java.lang.Thread.run(Thread.java:619)
Additional Comment #1 From fry 2010-05-03 05:37
yep, it's on the todo list. it hasn't been a higher priority since less
than 1% of our users are on 64-bit Linux. it requires a major rework of how
libraries are handled (not just platform/os anymore, have to switch 32/64
bits) so it's a significant amount of work, but will be useful for windows
and macosx as well, as more people start using 64-bit versions of those.
Additional Comment #2 From coldnebo 2010-05-03 12:14
no prob, I figured I'd enter it since I didn't see it in the bugs. thanks!
Additional Comment #3 From fry 2010-05-03 12:47
yes, thanks. it's very helpful to have things logged.
This bug is now being tracked here.