libjpcap.so: wrong ELF class
Status: Beta
Brought to you by:
jgood
Menu
▾
▴
#6 libjpcap.so: wrong ELF class
When I run tnv on my 64 bit AMD system, I am able to start the program, however when I load a file from tcpdump or wireshark, I get the error:
ian@goanna:~/Downloads/Security/tnv-0.3.8$ sudo ./tnv_startup.sh
[sudo] password for ian:
Starting tnv on Linux using JRE java...
PacketCapture: loading native library jpcap.. Exception in thread "AWT-EventQueue-0" java.lang.UnsatisfiedLinkError: /home/ian/Downloads/Security/tnv-0.3.8/lib/Linux/libjpcap.so: /home/ian/Downloads/Security/tnv-0.3.8/lib/Linux/libjpcap.so: wrong ELF class: ELFCLASS32 (Possible cause: architecture word width mismatch)
Further investigation reveals that the libjpcap.so included is for 32 bit systems and not compatible with 64 bit systems.
Attempting to compile jpcap-0.7 on my Ubuntu 9.10 system fails because of missing headers that I am not able to find in the package lists.
To resolve this issue, a 64 bit version of libjpcap.so should be included in the tnv distribution.
I think you may be trying to compile the wrong jpcap. Please try to compile:
https://sourceforge.net/projects/jpcap/
If you post a 64bit version, I will include it in the tnv download.
FYI. I see the same problem as the OP. I am running 64-bit Ubuntu 9.10 on an Intel Core 2 Duo.
I grabbed the gzip'ed tar of jpcap-0.01.16 from sourceforge and tried to follow the build instructions to the letter.
No joy. So I did a 'make clean' which seemed to work, and when I did 'make' things hummed along for a while and the java classes in 'util' built ok before I got a bunch of g++ compiler errors on jpcap.c as well as a complaint that libpcap.a and the libcap headers could not be found. So I installed the libcap0.8-dev packages. I did another 'make clean; make' which got rid of the libcap errors but left me with a complaint about not being able to find jni.h, followed by a bunch of g++ errors on jpcap.c again. I'm sorry to wimp out on you guys, but I have to move on today. If tnv bundles (or at least points to prebuilt) dependencies for x64 in the future, I'll definitely try it out. Maybe my notes will shave a few minutes off that effort. Cheers!