[Top][All Lists]

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

Re: Force link to local lib?

From: Luke M
Subject: Re: Force link to local lib?
Date: Mon, 24 Jan 2011 10:26:47 -0800 (PST)

Olaf Till wrote:
> 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
> _______________________________________________
> Help-octave mailing list
> address@hidden

Thank you for your reply.  I'm actually using tcsh, but yes they are set
correctly.  Here are relevant portions of my environment:

PATH=/data/personal/bin:<snip other stuff>
LD_LIBRARY_PATH=/data/personal/lib64:/data/personal/lib:<snip other stuff>
LDFLAGS=-L/data/personal/lib64 -L/data/personal/lib

And the Octave configuration:

  Source directory:            .
  Installation prefix:         /data/personal
  C compiler:                  /data/personal/bin/gcc450   -Wall -W -Wshadow
-Wformat -Wpointer-arith -Wmissing-prototypes -Wstrict-prototypes
-Wwrite-strings -Wcast-align -Wcast-qual -g -O2 -pthread
  C++ compiler:                /data/personal/bin/g++450  
-I/usr/include/freetype2    -Wall -W -Wshadow -Wold-style-cast -Wformat
-Wpointer-arith -Wwrite-strings -Wcast-align -Wcast-qual -g -O2
  Fortran compiler:            /data/personal/bin/gfortran450 -O
  Fortran libraries:            -L/data/personal/lib64 -L/data/personal/lib
-L/lib/../lib64 -L/usr/lib/../lib64
-L/data/personal/lib/gcc/x86_64-unknown-linux-gnu/4.5.0/../../.. -lgfortran

Unfortunately I'm out of tricks and I can't for the life of me understand
why liboctave and liboctinterp would want to link to /usr/lib64 first.  I
guess maybe autotools or libtool is prepending some expected library
locations, but I just don't know where to look.  In the build logs I get
these messages repeated a bunch of times:

libtool: link: warning: `/data/personal/lib64/' seems to be
libtool: link: warning: `/data/personal/lib64/' seems to be

Which is a dirty, filthy lie:

> ls /data/personal/lib64/ /data/personal/lib64/
/data/personal/lib64/*  /data/personal/lib64/*

What's extremely annoying is that and both have
those files listed explicitly on in the dependency_libs variable.
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]