[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #50510] 64-bit build issue
From: |
John W. Eaton |
Subject: |
[Octave-bug-tracker] [bug #50510] 64-bit build issue |
Date: |
Fri, 10 Mar 2017 17:36:39 -0500 (EST) |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Firefox/45.0 |
Follow-up Comment #2, bug #50510 (project octave):
suitesparse provides interfaces for both 32- and 64-bit integers. With
whatever package system we are using on OS X, it is configured to use "long
int" for 64-bit integers. That is not identical to int64_t, which is a
typedef for "long long int" on that system.
We don't get to choose what typedef is used for suitesparse if we are using
someone else's packaged version of it.
Yes, other systems could have similar issues. We build everything ourselves
on Windows and we use typedefs that match.
We could see the same for Linux systems if "long int" and "long long int" were
mixed. They are the same size. But we appear to be lucky there and everyone
seems to use "long int" and that's the same as what is used for "int64_t".
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?50510>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/