At 06:33 AM 4/1/2005, Nick Glencross wrote:

Having never had access to a Tru64 system, does that mean that parrot is compiled 64 bit?

Two initial comments:

* This is a platform that we've not had a chance to test on, so I'm grateful to see it tested on a new platform. It was hoped that it would work, but to stop the test failing it was supposed to skip them until formally tested. Why did the skipping not work though? What would the intsize attribute be (from config_lib.pasm I guess)

Not true. We've done successful compiles before on Tru64. Maybe as of 0.0.6 or something but
we were using Compaq's testdrive system and 64-bit gcc. At one time Parrot dir run on
both 64-bit Sparc and Alpha and I tested all these when doing the byte-ordering code.



* Secondly, any chance I can get access to other platforms, such as this one, to troubleshoot the problem? If not, perhaps I can instrument the code and have the results sent back to me...

Check out and see if testdrive is still available. I don't even remember the IPs or account info, nor do
I remember the URL to go to but you can get free shell accounts if they still offer it. Also, I had set
up an S/390 account at IBM for Daniel way back when and did a succesful compile there, but we
never got the JIT written and it fell off the map.


-Melvin




Reply via email to