[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 13:01:13 -0500 (EST) |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Firefox/45.0 |
URL:
<http://savannah.gnu.org/bugs/?50510>
Summary: 64-bit build issue
Project: GNU Octave
Submitted by: jwe
Submitted on: Fri 10 Mar 2017 06:01:12 PM UTC
Category: Configuration and Build System
Severity: 3 - Normal
Priority: 5 - Normal
Item Group: Build Failure
Status: None
Assigned to: None
Originator Name: jwe
Originator Email:
Open/Closed: Open
Discussion Lock: Any
Release: dev
Operating System: Mac OS
_______________________________________________________
Details:
This build is failing due to a 64-bit integer issue:
http://buildbot.octave.org:8010/builders/clang-osx
The failure happens because Octave is using int64_t (== "long long int" on OS
X systems) for octave_idx_type but suitesparse is configured to use "long int"
for 64-bit integers.
This shouldn't matter, right? They are both 8-byte integers. But no, passing
a pointer to long long int to a function that expects a pointer to long int is
an error.
In all fairness, this is not a clang or OS X problem. It would happen
anywhere. We just haven't noticed it until now because the typedefs on other
systems have happened to be consistent. But in a world where there are
independently compiled libraries, it seems there is little hope that everyone
will make the same choice. So, what to do?
I chose Mac OS as the OS category since that's where I noticed the failure,
but it could happen anywhere.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?50510>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
- [Octave-bug-tracker] [bug #50510] 64-bit build issue,
John W. Eaton <=