Re: Force link to local lib?

[Olaf Till]

On Fri, Jan 21, 2011 at 04:01:24PM -0800, Luke M wrote:
> 
> Apologies, this is not really an Octave question.
> 
> I'm working on RHEL 5.3 without root, so I've built many dependencies from
> scratch.  I've got 3.3.51+ running great, but I can't remember how I tricked
> Octave into using my local libstdc++.so (and similar files from my locally
> built gcc).  I've successfully built 3.3.55, but the blasted liboctave and
> liboctinterp shared objects decided to link to /usr/lib64/libstdc++.so.  I'm
> not sure how that's even possible, since I believe it requires my newer
> local version to build.
> 
> Both my LD_LIBRARY_PATH and LD_RUN_PATH contain my local directory with
> libstdc++.so before any others.  From what I've read I believe I have to
> rebuild, but I'm not sure what to do differently since I ran the exact same
> configure command from 3.3.51+.
> 
> Any ideas?  Thanks in advance.

If I remember right, LD_RUN_PATH must also already be exported during building
(or better also export LD_LIBRARY_PATH, it should at least do no harm). Have
you done that?

Olaf