Bill Hart wrote:
Cause of what David? MPIR 1.3.0 works absolutely fine on t2 if you set
the library paths correctly.
I'm not convinced it should be necessary to set LD_LIBRARY_PATH like that. It is
not with other 64-bit applications. But I may be mistaken
BTW, a 64-bit build of mpir 1.3.0 on
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 3
Bill Hart wrote:
2010/1/28 Dr. David Kirkby :
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 in /usr/local/lib is not
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 on ultrasparc2 machines,
I've just tried on an UltraSPAR
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 on ultrasparc2 machines,
including t2 (solaris) and gcc54
