Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Linux amd64 linking troubles (wrong ELF class: ELFCLASS32) #8

Closed
rogerallen opened this issue Apr 25, 2013 · 2 comments
Closed

Linux amd64 linking troubles (wrong ELF class: ELFCLASS32) #8

rogerallen opened this issue Apr 25, 2013 · 2 comments
Assignees
Labels
Milestone

Comments

@rogerallen
Copy link
Member

From the forum: https://groups.google.com/forum/?fromgroups=#!topic/overtone/7bQSJUUviBw

Hi,

I'm trying to get Shadertone working, but can't! I followed the instructions on the github (https://github.com/overtone/shadertone), but was unclear on how to run the project. I read the usage section but couldn't figure it out, so I decided to try lein repl to see if that would work. It didn't because I can't even load the overtone library without it crashing (something which I tested and can safely do in a new lein project). I recorded a terminal session of this and put it here: http://pastebin.com/raw.php?i=aqKebm0p.

Am I running the project incorrectly? Is this something wrong with my computer's configuration? Any help is greatly appreciated!

-Kane


The pastebin has this clue:

*** ERROR: dlsym load err '/home/chris/shadertone/target/native/linux/x86_64/libscsynth.so: undefined symbol: load'
Found 0 LADSPA plugins
*** ERROR: dlsym load err '/home/chris/shadertone/target/native/libopenal64.so: undefined symbol: load'
*** ERROR: dlsym load err '/home/chris/shadertone/target/native/liblwjgl64.so: undefined symbol: load'
*** ERROR: dlopen '/home/chris/shadertone/target/native/liblwjgl.so' err '/home/chris/shadertone/target/native/liblwjgl.so: wrong ELF class: ELFCLASS32'

Something is up with the mixture of elf32 and elf64 libs

@rogerallen
Copy link
Member Author

A workaround of renaming the 64-bit .so files and removing the 32-bit files seems to get past this issue.

Something like:

cd target/native
# overwrite the 32-bit libs with the 64-bit libs
mv liblwjgl64.so liblwjgl.so
mv libopenal64.so libopenal.so

@rogerallen
Copy link
Member Author

this should work just fine now with 0.2.0-SNAPSHOT

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant