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:Joel Uckelman (ucke@nomic.net)
Date:May 26, 2009 3:24:51 pm
List:net.java.dev.jna.users

Thus spake Timothy Wall:

Most likely the user is running a 64-bit system, and has set LD_LIBRARY_PATH or some other dynamic loader variable to point to the 32-bit library directory, which *shouldn't* be done if running a 64- bit executable.

It's also possible that JNA is using an incorrect load path to find whatever library is providing sysinfo. Do you provide an absolute path, or just the library name?

This is the call which loads libc:

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

We're loading it by name, not by path.

Where does this library reside on an arch linux system (both 32-bit and 64-bit versions)?

I would guess they'd be in /lib and /lib64. But that's only a hunch. I looked around in Google, but didn't turn up anything Arch-specific.