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

[JohnD]

> -----Original Message-----
> From: Philip Nienhuis [mailto:address@hidden
> Sent: Tuesday, December 09, 2014 12:29 PM
> To: address@hidden; address@hidden
> Subject: Fwd: RE: [MXE MinGW] miscompiled gcc for --enable64?
> 
> > Philip Nienhuis wrote:
> >>
> >> That surprises me.
> >>
> >> First of all, for me the patch from this bug report is needed to make
> >> a few OF packages compile:
> >> https://savannah.gnu.org/bugs/index.php?43318
> >> (I'd appreciate if a core dev could review that patch, please)
> >>
> >> But even with that patch, the following OF packages included in
> >> mxe-octave won't install at all with --enable-64:
> >> - image
> >> - odepkg
> >> - fl-core
> >> - netcdf
> >>
> >> Have you tried "pkg list" to see which packages do get installed
> >> successfully?
> >
> > <snip>
> >
> >>>> pkg list
> >> Package Name         | Version | Installation directory
> >> ---------------------+---------+-----------------------
> >>            actuarial  |   1.1.0 |
> >> C:\Octave\octave64\octave-3.8.2\share\octave\packages\actuarial-1.1.0
> >>       communications  |   1.2.0 |
> >> C:\Octave\octave64\octave-3.8.2\share\octave\packages\communications-
> 1.2.0
> >>              control  |   2.6.6 |
> >> C:\Octave\octave64\octave-3.8.2\share\octave\packages\control-2.6.6
> >>       data-smoothing  |   1.3.0 |
> >> C:\Octave\octave64\octave-3.8.2\share\octave\packages\data-smoothing-
> 1.3.0
> >>                dicom  |   0.1.1 |
> >> C:\Octave\octave64\octave-3.8.2\share\octave\packages\dicom-0.1.1
> >>                 fits  |   1.0.5 |
> >> C:\Octave\octave64\octave-3.8.2\share\octave\packages\fits-1.0.5
> >>              fl-core  |   1.0.0 |
> >> C:\Octave\octave64\octave-3.8.2\share\octave\packages\fl-core-1.0.0
> >>  fuzzy-logic-toolkit  |   0.4.5 |
> >>              general  |   1.3.4 |
> >> C:\Octave\octave64\octave-3.8.2\share\octave\packages\general-1.3.4
> >>             geometry  |   1.7.0 |
> >> C:\Octave\octave64\octave-3.8.2\share\octave\packages\geometry-1.7.0
> >>                image  |   2.2.2 |
> >> C:\Octave\octave64\octave-3.8.2\share\octave\packages\image-2.2.2
> >>                   io  |   2.2.5 |
> >> C:\Octave\octave64\octave-3.8.2\share\octave\packages\io-2.2.5
> >>       linear-algebra  |   2.2.0 |
> >> C:\Octave\octave64\octave-3.8.2\share\octave\packages\linear-algebra-
> 2.2.0
> >>                ltfat  |   2.0.1 |
> >> C:\Octave\octave64\octave-3.8.2\share\octave\packages\ltfat-2.0.1
> >>        miscellaneous  |   1.2.1 |
> >> C:\Octave\octave64\octave-3.8.2\share\octave\packages\miscellaneous-
> 1.2.1
> >>               netcdf  |   1.0.5 |
> >> C:\Octave\octave64\octave-3.8.2\share\octave\packages\netcdf-1.0.5
> >>               odepkg  |   0.8.4 |
> >> C:\Octave\octave64\octave-3.8.2\share\octave\packages\odepkg-0.8.4
> >>                optim  |   1.4.0 |
> >> C:\Octave\octave64\octave-3.8.2\share\octave\packages\optim-1.4.0
> >>           quaternion  |   2.2.2 |
> >> C:\Octave\octave64\octave-3.8.2\share\octave\packages\quaternion-2.2.2
> >>               signal  |   1.3.0 |
> >> C:\Octave\octave64\octave-3.8.2\share\octave\packages\signal-1.3.0
> >>              sockets  |   1.0.8 |
> >> C:\Octave\octave64\octave-3.8.2\share\octave\packages\sockets-1.0.8
> >>              specfun  |   1.1.0 |
> >> C:\Octave\octave64\octave-3.8.2\share\octave\packages\specfun-1.1.0
> >>          statistics  |   1.2.3 |
> >> C:\Octave\octave64\octave-3.8.2\share\octave\packages\statistics-1.2.3
> >>               struct  |  1.0.10 |
> >> C:\Octave\octave64\octave-3.8.2\share\octave\packages\struct-1.0.10
> >>                  tsa  |   4.2.7 |
> >> C:\Octave\octave64\octave-3.8.2\share\octave\packages\tsa-4.2.7
> >>              windows  |   1.2.1 |
> >> C:\Octave\octave64\octave-3.8.2\share\octave\packages\windows-1.2.1
> >>               zenity  |   0.5.7 |
> >> C:\Octave\octave64\octave-3.8.2\share\octave\packages\zenity-0.5.7
> >
> > So you also have the image pkg missing.
> >
> >
> > What I get when trying to install fl-core, netcdf and odepkg:
> >
> > ====================== fl-core ====================
> >
> >  >> cd ([OCTAVE_HOME filesep "src"])
> >
> >  >> pkg install -verbose fl-core-1.0.0.tar.gz mkdir
> > :
> > make: *** [fl_compose.oct] Error 1
> >
> >
> > ======================== netcdf ===========================
> >
> >  >> pkg install -verbose netcdf-1.0.5.tar.gz
> > :
> > __netcdf__.cc: In function 'octave_value_list Fnetcdf_inqDimIDs(const
> > octave_value_list&, int)':
> > __netcdf__.cc:2000:29: error: call of overloaded
'octave_value(Array<int>&)'
> > is ambiguous
> > :
> > :
> > .....and so on.
> >
> > =========================== odepkg =====================
> >
> >  >> pkg install -verbose odepkg-0.8.4.tar.gz <configure>
> > :
> > :
> > make: *** [odepkg_octsolver_radau.o] Error 1
> > make: Leaving directory `/tmp/oct-6/odepkg/src'
> >  >>
> >
> >
> > All of these installation failures seem to be related to some int
> > conversion.
> > Perhaps it is due to changes in version 3.9.0+? I don't know.
> >
> > Philip
> >
> >
> > JohnD's reply:
> > --
> >
> > Image 2.2.2 installed on the list above
> 
> Yep I missed that, sorry.
> 
> > I get a few warnings whilst installing some of the packages, but no
> > errors, so it is interesting that there are differences between our
systems.
> >
> > I am compiling currently with the --enable-windows-64
> > --enable-octave=default, so will see if that behaves any differently.
> 
> Last night I cross-built 3.8.2 w/o the patch from bug #43318 with a fresh
mxe-
> octave clone (using only --enable-64; that automatically enables --enable-
> windows-64 as it shows in the Makefile).
> 
> After running build-packages, the following OF packages:
>   image,
>   fl-core,
>   odepkg and
>   netcdf
> are still missing due to compile errors.
> So indeed it seems mxe-octave does not deliver guaranteed identical cross-
> builds.... or there's another difference between my and your build system
that
> I've overlooked.
> 
> Tonight I'll try a 3.9.0+ build w/o patch from #43318 and see how that
handles
> OF packages.
> 
> BTW as of lately my cross-builds often get stuck while building libmng; it
stops
> with a complaint about mismatching autoconf versions (1.4 versus 1.4.2
IIRC).
> 
> Philip

I haven't had any issues with libmng on my system - looking in the log file,
I see a 
Main::scan_file() called too early to check prototype.
Out of interest what -j option is used for make for you?

Libtool is v 2.4.2, the version with libmng is 2.4, however calls
autoreconfig in the .mk file.
Perhaps it needs the force option?