Re: mxe-octave: build fails with ".../unistd-wrappers.h:56:8: error: 'pid_t' does not name a type"

[Philip Nienhuis]

Philip Nienhuis wrote:
> John W. Eaton wrote:
> > On 06/19/2016 09:31 AM, PhilipNienhuis wrote:
> > > John W. Eaton wrote
> > > > > On Fri, Jun 17, 2016 at 14:31:41 -0700, PhilipNienhuis wrote:
> > > > > > Octave-dev tip (21942:aab79a1885cc) fails to build in mxe-octave (tip
> > > > > > 4157:fcf0410f7055) while building (AFAICS)
> > > > > > libinterp/corefcn/oct-tex-lexer.cc with errors along the lines of:
> > > > > >
> > > > > > :
> > > > > /home/philip/devel/octdev/mxe/mxe_64b_20160617/tmp-default-octave/octave-4.1.0+/liboctave/wrappers/unistd-wrappers.h:56:8:
> > > > >
> > > > > > error: 'pid_t' does not name a type
> > > > > >   extern pid_t octave_fork_wrapper (void);
> > > >
> > > > I have a patch in progress that will fix the Windows build.  I'll
> > > > try to
> > > > finish it and push this weekend.
>
> <snip>
>
> > > Still dev octave doesn't cross-build for me.
> > > Excerpt from log with a bit of preceding context to show where it
> > > breaks:
> >
> > I don't know what's causing trouble for you.  It works for me at least
> > as far as building Octave.  I'm having some problems with parallel "make
> > install" that seem to be due to targets being made multiple times in
> > parallel because of move-if-change rules.  But that's a separate issue
> > and I don't think related to my recent changes.
>
> My build was configured with --enable-windows-64; was your build for 32
> bits?
> I'm trying a 32-bit build now. Hopefully tomorrow morning I'll know more.

Exact same error :-(

g++ -o src/i686-w64-mingw32-mkoctfile -Dgnulib='' -Doctave_idx_type=int 
-I. 
-I/home/philip/devel/octdev/mxe/mxe_32b_20160620/tmp-default-octave/octave-4.1.0+ 
-O2 -g 
-I/home/philip/devel/octdev/mxe/mxe_32b_20160620/tmp-default-octave/octave-4.1.0+/src 
src/i686-w64-mingw32-mkoctfile.cc
src/i686-w64-mingw32-mkoctfile.cc:38:29: fatal error: unistd-wrappers.h: 
No such file or directory
 #include "unistd-wrappers.h"
                             ^
compilation terminated.

Well, I'll start a build with JOBS=1 although I doubt -like you- that it 
will make any difference.


Philip