[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[MXE mingw] "unknown type name 'int64_t'" with --enable-64 when compilin
From: |
Philip Nienhuis |
Subject: |
[MXE mingw] "unknown type name 'int64_t'" with --enable-64 when compiling mex files |
Date: |
Fri, 22 Aug 2014 09:55:30 -0700 (PDT) |
While trying to install the io package on a MXE-cross-built Octave with
--enable64, I get the following error messages:
:
mkoctfile --mex __num2char__.c
In file included from
C:\Octave\octave64-3.8.2\include\octave-3.8.2\octave/mexproto.h:71:0,
from
C:\Octave\octave64-3.8.2\include\octave-3.8.2\octave/mex.h:67,
from __num2char__.c:16:
C:\Octave\octave64-3.8.2\include\octave-3.8.2\octave/mxarray.h:89:9: error:
unknown type name 'int64_t'
typedef int64_t mwSize;
^
C:\Octave\octave64-3.8.2\include\octave-3.8.2\octave/mxarray.h:90:9: error:
unknown type name 'int64_t'
typedef int64_t mwIndex;
^
C:\Octave\octave64-3.8.2\include\octave-3.8.2\octave/mxarray.h:91:9: error:
unknown type name 'int64_t'
typedef int64_t mwSignedIndex;
^
mkoctfile could compile the "regular" .oct files fine and they work fine as
well (compiled individually). It is just the two mex files that give errors.
So, AFAIU 'int64_t' doesn't seem to be defined; I grepped around in
<octave>/include/ but couldn't find out where the definition is.
It has something to do with MXE or Mingw; because on my Linux 64bit box, the
io package installs (and works) fine in Octave built with --enable-64.
Any suggestions or fixes?
Thanks,
Philip
--
View this message in context:
http://octave.1599824.n4.nabble.com/MXE-mingw-unknown-type-name-int64-t-with-enable-64-when-compiling-mex-files-tp4666187.html
Sent from the Octave - Maintainers mailing list archive at Nabble.com.
- [MXE mingw] "unknown type name 'int64_t'" with --enable-64 when compiling mex files,
Philip Nienhuis <=