numarray on 64 bits
![](https://secure.gravatar.com/avatar/b6c3a8039062726b0600fc5de0dafee7.jpg?s=120&d=mm&r=g)
Did anybody use numarray on a 64 bits platform ? (e.g. SGI/Irix) The package works on our 64 bits platforms... using 32 bits mode, but not using 64 mode. Big crash in _ufunc... Is there a flag to set somewhere, trick, hint, noway ? -MP- ----------------------------------------------------------------------- Marc POINOT Alias: marcvs Email: poinot@onera.fr ONERA -MFE/DSNA/ELSA Tel: 01.46.73.42.84 Info: elsa-info@onera.fr 29, Div. Leclerc Fax: 01.46.73.41.66 Site: 92322 Chatillon FRANCE Project: elsA Web: http://www.onera.fr
![](https://secure.gravatar.com/avatar/faf9400121dca9940496a7473b1d8179.jpg?s=120&d=mm&r=g)
On Thu, 2004-04-29 at 03:51, Marc Poinot wrote:
Did anybody use numarray on a 64 bits platform ?
Numarray has been used on Compaq Alpha/Tru64 and also SGI Altix, but neither is an everyday platform for us at STScI.
(e.g. SGI/Irix) The package works on our 64 bits platforms... using 32 bits mode, but not using 64 mode. Big crash in _ufunc...
This is probably a bug which has was created since we dropped Tru64 at STScI. A gdb traceback would be useful here to help understand where the crash occurred. Generally, crashes result from the improper use of ints/longs in the numarray C-code.
Is there a flag to set somewhere, trick, hint, noway ?
There's really only one flag that matters for 64-bit operation on UNIX: LP64. It's controlled/propagated in the file generate.py. LP64 asserts that longs and pointers are 64-bit, while ints remain 32-bit. I imagine you've already set this. Regards, Todd -- Todd Miller <jmiller@stsci.edu>
participants (2)
-
Marc Poinot
-
Todd Miller