library error ok

stabu · 08-18-2008, 04:34 PM

OK, doing some mpi compiling on openmpi, but I think it's a general fault I have. My prog compiles fine. But when running is I get:

Code:

a.out: error while loading shared libraries: ibc.so.6: cannot open shared object file: No such file or directory

See that ibc? WTF? Obviously I run this error in google, and I get all the people who have mistyped libc. But this is not an error, it's actually ibc.

My system has no such library. Does anybody know how I might go about troubleshooting this? I thought I'd do a ldd on my executable and this library does not appear:

Code:

libm.so.6 => /lib64/libm.so.6 (0x00002ba425829000)
libmpi.so.0 => /usr/local/lib/libmpi.so.0 (0x00002ba425aac000)
libopen-rte.so.0 => /usr/local/lib/libopen-rte.so.0 (0x00002ba425d3f000)
libopen-pal.so.0 => /usr/local/lib/libopen-pal.so.0 (0x00002ba425f9a000)
libdl.so.2 => /lib64/libdl.so.2 (0x00002ba4261f8000)
libnsl.so.1 => /lib64/libnsl.so.1 (0x00002ba4263fc000)
libutil.so.1 => /lib64/libutil.so.1 (0x00002ba426614000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x00002ba426817000)
libc.so.6 => /lib64/libc.so.6 (0x00002ba426a32000)
/lib64/ld-linux-x86-64.so.2 (0x00002ba42560c000)

As yo can see, all the usual suspects are there, but no ibc of course.
Does any body know of any tool I coudl use to find out where this odd library is coming up?

I did a reinstall of my openmpi and I get the same thing. I don't think this has anythoign to do with my PATH or LD_LIBRARY_PATH because I simply do not have that library... my only guess is that, in the past, I inadvertently edited some file, which now demands that my openmpi programs be linked to a nonexistent library.

Ideas welcome

cheers.

keratos · 08-18-2008, 04:51 PM

its obviously libc.so.6

ibc seems to have the 'l' missing

could it be a corrupt config file or makefile?

i dont know enough about your platform but I would do a grep on the files in your build tree, search for "ibc" or something and see if its an error in a build / config / makefile

stabu · 08-18-2008, 05:10 PM

Hi keratos,

Thanks for the reply .. this is just getting funnier and funnier ... I now do a google search for ibc.so.6 and this here thread that I started comes up first! So I'm even making it harder for myself :-D

Yes, I think you're right .. I've been doing a grep "[^l]ibc" on a number of my various lib files ... there's no Makefile really ... but MPI is a complicated beast ... I'll keep grepping, it'll come out of the woodwork soon enough :-)!

stabu · 08-18-2008, 05:33 PM

Hmmm ... well I've kind of semi-solved this.

The clue came from man ldd

Code:

BUGS
       ldd does not work on a.out shared libraries.

I remembered that it's probably not a good habit to keep compiling to a.out all the time. So I re-tested giving it an "-o" option name.

However, the program actually ran properly then. SO I don't get to find out why ibc.so.6 is coming up. Seems to be parsing error of some sort if one uses a.out.

Thanks for the interest!

PD. Good, this means I don't have to run

Code:

grep -R "[^l]ibc\.so\.6" /

on my 1TB HD tonight :-D

ta0kira · 08-18-2008, 07:36 PM

Quote:

Originally Posted by stabu

I remembered that it's probably not a good habit to keep compiling to a.out all the time. So I re-tested giving it an "-o" option name.

a.out is the default file name for gcc, but it's generally in ELF-32 format and not in a.out format.

Have you run ldconfig recently? Are you using a makefile? If so, did you write it by hand, or did an IDE write it for you via e.g. automake?
ta0kira