RE: [MXE MinGW] miscompiled gcc for --enable64?

[JohnD]

> -----Original Message-----
> From: Philip Nienhuis [mailto:address@hidden
> Sent: Wednesday, December 10, 2014 3:39 PM
> To: JohnD; address@hidden
> Subject: Re: [MXE MinGW] miscompiled gcc for --enable64?
> 
> JohnD wrote:
> >
> >
> >> -----Original Message-----
> >> From: Philip Nienhuis [mailto:address@hidden
> >> Sent: Tuesday, December 09, 2014 4:42 PM
> >> To: JohnD; address@hidden
> >> Subject: Re: [MXE MinGW] miscompiled gcc for --enable64?
> >>
> >> Philip Nienhuis wrote:
> >>>> After running build-packages, the following OF packages:
> >>>>     image,
> >>>>     fl-core,
> >>>>     odepkg and
> >>>>     netcdf
> >>>> are still missing due to compile errors.
> >>
> >> Same on 3.9.0+ cross-built with --enable-64.
> >> In addition, building ltfat also breaks (probably also on 3.8.2 but I
> > can't check
> >> right now):
> >>
> >> ======================================
> >> :
> >> C:/Programs/Octave/octave64-3.9.0+/bin/mkoctfile-3.9.0+.exe -Wall
> >> -mex mex_dll_core.c pa_dll_playrec.c ltfatresample.c \
> >>                        -L. -lportaudio -I. -I../../src/thirdparty
> >> -DIS_OCTAVE -DHAVE_PORTAUDIO      -o playrec.mex
> >> In file included from
> >> C:\Programs\Octave\octave64-3.9.0+\include\octave-
> >> 3.9.0+\octave/mexproto.h:71:0,
> >>                    from
> >> C:\Programs\Octave\octave64-3.9.0+\include\octave-
> 3.9.0+\octave/mex.h:67,
> >>                    from mex_dll_core.c:88:
> >> C:\Programs\Octave\octave64-3.9.0+\include\octave-
> >> 3.9.0+\octave/mxarray.h:89:9:
> >> error: unknown type name 'int64_t'
> >>    typedef int64_t mwSize;
> >>            ^
> >> C:\Programs\Octave\octave64-3.9.0+\include\octave-
> >> 3.9.0+\octave/mxarray.h:90:9:
> >> error: unknown type name 'int64_t'
> >>    typedef int64_t mwIndex;
> >>            ^
> >> C:\Programs\Octave\octave64-3.9.0+\include\octave-
> >> 3.9.0+\octave/mxarray.h:91:9:
> >> error: unknown type name 'int64_t'
> >>    typedef int64_t mwSignedIndex;
> >>            ^
> >> make[1]: *** [all] Error 1
> >> ======================================
> >>
> >>
> >> Philip
> >
> >
> >
> > You are using the latest mxe-octave repo and installing packages from
> > the octave/src directory ?
> 
> Absolutely sure, save for the patch from JWE 17 hours ago:.
> 
> mxe-octave:
> ===========
> address@hidden mxe64_20141208]$ hg -v summary
> parent: 3755:bc32b686d0f5 tip
>   default-octave: add patch for successful compile of current default
branch
> branch: default
> bookmarks: *@
> 
> (All I did was wipe the isatty patch for octave.mk & adapt version &
> SHA1 chksum in octave,mk.
> Sometimes I also update OF linear-algebra as it has a bug (fixed by JWE
long
> ago) in (IIRC) iscomplex(). OF linear-algebra actually needs a new bug fix
> release.)
> 
> My system (Mageia-4 64bits)
> =========
> address@hidden mxe64_20141208]$ uname -a Linux deskprn 3.14.24-desktop-
> 1.mga4 #1 SMP Sat Nov 15 23:54:03 UTC 2014
> x86_64 x86_64 x86_64 GNU/Linux
> 
> address@hidden mxe64_20141208]$ gcc --version gcc (GCC) 4.8.2 Copyright
(C)
> 2013 Free Software Foundation, Inc.
> 
> glibc:
> 2.18 9.5m.ga4 x86_64
> 
> 
> Once Octave is installed (extracted) on Windows 7 Prof. 64 bit, I do:
> 
> cd ([OCTAVE_HOME filesep "src"])
> build_packages
> 
> 
> Do we conclude that mxe-octave does not fully guarantee identical builds
from
> the one build box to the next? It sure looks like that,
> 
> Both my Linux boxen are Mageia-4 64 bit. I could try again with
> --enable-64 on my laptop, though, as that also has Mageia-4 32bit.
> Is it possible at all to cross-build 64 bit Octave on a 32-bit box?
> 
> 
> Philip

Either not identical builds, OR the target machines run differently ?
Ie: does it behave differently on your windows machine vs my windows machine
with a installer that was built on a common machine?