OK, the problem is as follows. For very straightforward C programs, no
problems occur on t2 because the compiler emits inline code for
everything. However, once the program becomes too complicated for it
to do this, it uses libgcc:
http://gcc.gnu.org/onlinedocs/gccint/Libgcc.html
The problem is,
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
2010/1/28 Dr. David Kirkby david.kir...@onetel.net:
Bill Hart wrote:
Hi all,
it is with pleasure that we (finally) officially release MPIR 1.3.0.
It is available at our website http://www.mpir.org/
Please note the following important things:
* I have been unable to get any tests to pass
2010/1/28 Dr. David Kirkby david.kir...@onetel.net:
Bill Hart wrote:
Hi all,
it is with pleasure that we (finally) officially release MPIR 1.3.0.
It is available at our website http://www.mpir.org/
Please note the following important things:
* I have been unable to get any tests to pass
So on t2 there is no /usr/local/lib/sparcv9, so that's a bit useless!
Does this mean t2 is not capable of running 64 bit binaries?
2010/1/28 Dr. David Kirkby david.kir...@onetel.net:
Bill Hart wrote:
Hi all,
it is with pleasure that we (finally) officially release MPIR 1.3.0.
It is
On t2 all the tests fail, complaining of the same issue. If I actually
go into the tests directory and run one of the test scripts directly,
here is what it does:
./t-modlinv
ld.so.1: t-modlinv: fatal: libmpir.so.8: open failed: No such file or directory
Killed
So let's see what the script does:
So it can't find libmpir.so.8. But I don't see why.
echo $LD_LIBRARY_PATH
/usr/lib/sparcv9:/home/wbhart/mpir-1.3.0/.libs
Total random guess: could it be that you need this to be in your
DYLD_LIBRARY_PATH, too?
-cc
--
To post to this group, send email to sage-support@googlegroups.com
To
As far as I know that is only necessary on OS X. Anyhow, I tried it
just in case, and no change.
Thanks for the suggestion though.
Bill.
2010/1/28 Craig Citro craigci...@gmail.com:
So it can't find libmpir.so.8. But I don't see why.
echo $LD_LIBRARY_PATH
OK, on gcc54 only the C++ tests fail. But they always did. There is
actually a library missing from the machine which is needed to run
binaries compiled by the C++ compiler. All the C test binaries pass on
gcc54.
So the only issue is actually on t2. Basically I think there is a
whole pile of
Bill Hart wrote:
2010/1/28 Dr. David Kirkby david.kir...@onetel.net:
The problem is that 64-bit libraries should never be in /usr/local/lib.
Instead they should be in /usr/local/lib/sparcv9.
I am not installing MPIR on these machines, as I do not have root
access on either. Thus whatever is
Bill Hart wrote:
So on t2 there is no /usr/local/lib/sparcv9, so that's a bit useless!
Does this mean t2 is not capable of running 64 bit binaries?
No, since gcc is not installed under /usr/local, there is no
/usr/local/lib/sparcv9. What few programs do exist in /usr/local are probably
just
2010/1/28 Dr. David Kirkby david.kir...@onetel.net:
Bill Hart wrote:
2010/1/28 Dr. David Kirkby david.kir...@onetel.net:
The problem is that 64-bit libraries should never be in /usr/local/lib.
Instead they should be in /usr/local/lib/sparcv9.
I am not installing MPIR on these machines, as
One sensible solution would seem to be to set
LD_LIBRARY_PATH_64=/usr/local/gcc-4.4.1-sun-linker/lib/sparcv9 on t2,
but this actually doesn't seem to work. I'm not sure why.
However it seems that one can just add
/usr/local/gcc-4.4.1-sun-linker/lib/sparcv9 to the LD_LIBRARY_PATH (it
doesn't
On 28 January 2010 23:46, Bill Hart goodwillh...@googlemail.com wrote:
One sensible solution would seem to be to set
LD_LIBRARY_PATH_64=/usr/local/gcc-4.4.1-sun-linker/lib/sparcv9 on t2,
but this actually doesn't seem to work. I'm not sure why.
However it seems that one can just add
14 matches
Mail list logo
