The problem you have is with the location of the file liblibsigar-x86_64-linux.so.
This file needs to be located in the same directory where you run the sigar.jar or is available on the classpath when you run the Java VM.
Setting the class path can be done in the users login environment, but is commonly done using the -cp (-classpath) option like: java -cp /path/to/dir/with/lib
Hope that helps.
You are right, thanks for the reply.
But I dont have that shared library. So I wanted to know how can I build one?
There are lot of other shared libraries in the lib folder that has the sigar.jar file as well, but not the one that it is expecting. So I thought of building it on my own, but I did not find how I can build it on the Hyperic SIGAR website.
No, I have not build the codebase on my own.
I am not sure why the application asks for the shared obj with that name. I have tried running java -jar sigar.jar on a fresh Red hat Linux 64 bit machine and it threw the same error.
May be its an code problem.
BTW the name of the file that the it is asking is 'liblibsigar-x86_64-linux.so' and not liblibsigar-amd64-linux.so
Why is there a difference x86, amd? is it Intel chipset and AMD chipset?
This is an accurate "brief" history of the amd64 nomenclature from wikipedia:
History of AMD64
AMD64 was created as an alternative to Intel and Hewlett Packard's radically different IA-64 architecture. Originally announced in 1999 with a full specification in August 2000, the architecture was positioned by AMD from the beginning as an evolutionary way to add 64-bit computing capabilities to the existing x86 architecture, as opposed to Intel's approach of creating an entirely new 64-bit architecture with IA-64.
The first AMD64-based processor, the Opteron, was released in April 2003.