Originally Posted by unix1adm
I thought I needed this package but I have an x86_64 kernel loaded.
I can't tell if you understand. That package is for ia64. You have x86_64 in which 32 bit mode support is there by default. You don't need to add any package for the basic 32 bit support.
You do need to have all the 32 bit .so files that the application needs.
opsec/bin/LeaDataSource: error while loading shared libraries:
libelf.so.1: wrong ELF class: ELFCLASS64
I've never see that failure. I don't quite understand it. I thought that was a malfunction you would see running 32 bit applications in 64 bit Windows but Linux is smarter.
We often have both a 64 bit and 32 bit version of the same named .so file (or for Windows the same .dll file). If both are in the search path (LD_LIBRARYPATH in Linux) Windows will find whichever is first in search sequence and if it is the wrong size fail. Linux will find the first one and if it is the wrong bit size skip it and continue the search and find the second one.
I'm not sure what is different about your program or environment that it finds the 64 bit .so and complains about it.
In what I think is the same situation, my experience is it skips the 64 bit .so and then complains that the .so wasn't found.
Clearly the first thing to do is install the required 32 bit .so file. That is all I have needed to do. But your error message makes it seem that you might also need to make sure the 32 bit one is found before the 64 bit one in search sequence.
That's a nice link and I just bookmarked it for any situations in which the yum provides
command fails to give me the info I need. But can you tell me why that web page might be your first choice before even trying yum provides
From my limited knowledge I think yum provides
would be a better (specific to the version and repositories you have configured) normal method for answering the question "which package provides the specific file that is missing at the moment".
You might get some joy from running 'ldd opsec/bin/LeaDataSource' and see if any libraries are 'not found'.
I also find ldd
is a better first line method for finding out which .so files I'm going to need. After I've gotten all the .so files that ldd tells me I will need, then I use the error messages from trying to run the application to tell me about any other .so files I really need.