8 messages in net.java.dev.jna.usersRe: [jna-users] UnsatisfiedLinkError ...
FromSent OnAttachments
Joel UckelmanMay 25, 2009 2:55 pm 
Timothy WallMay 25, 2009 5:42 pm 
Joel UckelmanMay 26, 2009 1:53 pm 
Timothy WallMay 26, 2009 1:58 pm 
Joel UckelmanMay 26, 2009 2:08 pm 
Timothy WallMay 26, 2009 3:17 pm 
Joel UckelmanMay 26, 2009 3:24 pm 
Timothy WallMay 27, 2009 11:31 am 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:Re: [jna-users] UnsatisfiedLinkError due to invalid ELF headerActions...
From:Timothy Wall (twal@dev.java.net)
Date:May 25, 2009 5:42:44 pm
List:net.java.dev.jna.users

This is most likely an architecture mismatch, either 32-bit code trying to load 64-bit code or vice versa.

This could happen if running a 64-bit JVM but only having the 32-bit system libraries in LD_LIBRARY_PATH (or in this case, jna.library.path, which is where JNA will look for the library).

On May 25, 2009, at 5:55 PM, Joel Uckelman wrote:

I've had a bug report with the following error message:

java.lang.UnsatisfiedLinkError: Unable to load library 'c': /usr/lib/ libc.so: invalid ELF header

All I know is what I can tell from the stack trace, namely that this line is the source of the exception,

public static final Libc INSTANCE = (Libc) Native.loadLibrary("c", Libc.class);

and that the user is running Arch Linux. I have no way of contacting the user, so I can't ask for more information. Can anyone suggest what might cause such an exception? This has never happend for me on my own (Fedora) Linux system.