Bill Hart wrote:
Ah, got it. LD_LIBRARY_PATH_64 needs to also contain
/home/wbhart/mpir-1.3.0/.libs. Basically if LD_LIBRARY_PATH_64 is not
specified at all, i.e. left blank, the linker uses whatever is in
LD_LIBRARY_PATH. Otherwise it uses LD_LIBRARY_PATH_64 exclusively,
which means that *all* 64 bit library paths must be in
LD_LIBRARY_PATH_64.
So, in order to make MPIR work on t2, we'd need LD_LIBRARY_PATH_64 to
be set globally for users *and* we'd need libtool to recognise that it
needs to set LD_LIBRARY_PATH_64.
Unfortunately libtool doesn't do this automatically. So this is seems
to be a bug in the version of libtool we use. Another solution is to
set LD_LIBRARY_PATH_64 to include $LD_LIBRARY_PATH. This actually
works because the substitution is done live by the shell. In other
words, if LD_LIBRARY_PATH_64 is set to
/usr/local/gcc-4.4.1-sun-linker/lib/sparcv9:$LD_LIBRARY_PATH for all
users of t2 globally, I believe MPIR will work just fine on that
machine.
Bill.
I do not believe it is correct to add the sparcv9 directory to LD_LIBRARY_PATH,
though I accept it might solve the issue. If anything, that would be added to
LD_LIBRARY_PATH_64, but that is not working here.
I would speak to the libtool developers - I know Ralf is very helpful, and has
an account on 't2'. Perhaps he can solve this.
Are you using the latest libtool ? If not, an upgrade might work.
Dave
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org
