From: Vincent Belaïche on
Dear all,

I made a shared library libfoo.so to be linked with some application;
but the link does not work and I get the message that libfoo.so uses
something in libstdc++.so.6 that needs GLIBCXX_3.4.9 that is missing.

Sorry if that sort of questions comes again and again in this forum, I
am a newbie on Linux.

I am using a Linux RedHat 5 64bit machine. I suspect that there is some
issue with some compatibility libraries that is not installed, or maybe
this is connected with 64bits/32bits compatibility.

I would be very grateful to anyone with a clue.

Vincent.

PS: to make things worst, libfoo.so is supposed then to work also on
32bits machines, I don't know how to ensure this. I have set
LD_LIBRARY_PATH to point on the lib directory rather than on the lib64
directory, is that sufficient ?
From: Vincent Belaïche on
Hello,

Sorry for the distrubance, it seems that I solved this issue, actually
the application was launched by a script that was tampering with
LD_LIBRARY_PATH, which caused the dynmic link problem.

Vincent Bela�che a �crit :
> Dear all,
>
> I made a shared library libfoo.so to be linked with some application;
> but the link does not work and I get the message that libfoo.so uses
> something in libstdc++.so.6 that needs GLIBCXX_3.4.9 that is missing.
>
> Sorry if that sort of questions comes again and again in this forum, I
> am a newbie on Linux.
>
> I am using a Linux RedHat 5 64bit machine. I suspect that there is some
> issue with some compatibility libraries that is not installed, or maybe
> this is connected with 64bits/32bits compatibility.
>
> I would be very grateful to anyone with a clue.
>
> Vincent.
>
> PS: to make things worst, libfoo.so is supposed then to work also on
> 32bits machines, I don't know how to ensure this. I have set
> LD_LIBRARY_PATH to point on the lib directory rather than on the lib64
> directory, is that sufficient ?