Re: [mpir-devel] Re: [sage-devel] Re: MPIR 1.3.0 released (at last)

2010-01-30 Thread Bill Hart
2010/1/30 Dr. David Kirkby : > BTW, a 64-bit build of mpir 1.3.0 on an HP-C3600, running HP-UX 11.11B, > results in the results shown below. This is with a PA-RISC processor - I do > not have access to any of the newer Itanium machines. > > This is really good news, as an HP-UX port of Sage seems

Re: [mpir-devel] Re: [sage-devel] Re: MPIR 1.3.0 released (at last)

2010-01-30 Thread Bill Hart
If you don't want to change LD_LIBRARY_PATH, change LD_LIBRARY_PATH_64 as I explained. It's this simple: 1) GCC NEEDS** complicated binaries to link against libgcc (read the supplied references online or google it yourself) 2) Thus the linker NEEDS*** the path to the 64 bit libgc

Re: [mpir-devel] Re: [sage-devel] Re: MPIR 1.3.0 released (at last)

2010-01-30 Thread Bill Hart
Sorry, I pressed send before sanitising. I didn't intend to post the expletives. Apologies for any offence. I am just a bit frustrated at the moment, probably for reasons that have nothing to do with this conversation, sorry. Bill. 2010/1/30 Bill Hart : > 2010/1/30 Dr. David Kirkby : >> Bill Har

Re: [mpir-devel] Re: [sage-devel] Re: MPIR 1.3.0 released (at last)

2010-01-30 Thread Bill Hart
2010/1/30 Dr. David Kirkby : > 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 mistak

[mpir-devel] Re: [sage-devel] Re: MPIR 1.3.0 released (at last)

2010-01-30 Thread Dr. David Kirkby
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