Re: Windows Octave compilation

[Marco Atzeri]

On 06/07/2014 23:35, Philip Nienhuis wrote:
> ijourneaux wrote
> > John Donoghue-2 wrote
> > > I did compile Octave a few days ago with the native mingw and pushed a
> > > few
> > > changed to mxe-octave to support the build, however, as Philip said - it
> > > is
> > > far easier to cross compile it.
> > If you created a native mingw build, could you check to see if this
> > creates a segfault.
> >
> > 1. open a command window
> > 2. start octave-cli
> > 3. run the following
> > test imread
> > exit(0)
> >
> > The MXE octave build segfaults.

also the cygwin build segfautls

$ hg tip
changeset:   18873:85d04dfdeac3
bookmark:    @
tag:         tip
parent:      18872:4586051a5ff1
parent:      18871:23e511f3395d
user:        John W. Eaton <address@hidden>
date:        Fri Jun 27 17:09:46 2014 -0400
summary:     maint: Periodic merge of gui-release to default.


> A recent 4.1.0+ version (cross-compiled) still segfaults (I get a core
> dump). See attached pic
> <http://octave.1599824.n4.nabble.com/file/n4665285/imread_410%2B_segfault.png>
> (hopefully uploading to Nabble works)
> I think I reported that earlier. BTW that sequence runs fine on Linux.
>
> John D indicated that native building should work. That will make debugging
> easier, as Octave can then be run in its build environment.
> I still don't have time/priority to help you here (and summer holiday is
> looming), sorry.
>
> Philip

Marco