[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Force link to local lib?

From: Luke M
Subject: Force link to local lib?
Date: Fri, 21 Jan 2011 16:01:24 -0800 (PST)

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 (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/  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 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.
View this message in context:
Sent from the Octave - General mailing list archive at

reply via email to

[Prev in Thread] Current Thread [Next in Thread]