octave-maintainers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: mxe-octave: build fails with ".../unistd-wrappers.h:56:8: error: 'pi


From: Mike Miller
Subject: Re: mxe-octave: build fails with ".../unistd-wrappers.h:56:8: error: 'pid_t' does not name a type"
Date: Fri, 17 Jun 2016 16:08:22 -0700
User-agent: Mutt/1.6.0 (2016-04-01)

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);
>         ^
> /home/philip/devel/octdev/mxe/mxe_64b_20160617/tmp-default-octave/octave-4.1.0+/liboctave/wrappers/unistd-wrappers.h:70:8:
> error: 'pid_t' does not name a type
>  extern pid_t octave_getpgrp_wrapper (void);
>         ^
> /home/philip/devel/octdev/mxe/mxe_64b_20160617/tmp-default-octave/octave-4.1.0+/liboctave/wrappers/unistd-wrappers.h:72:8:
> error: 'pid_t' does not name a type
>  extern pid_t octave_getpid_wrapper (void);
>         ^
> /home/philip/devel/octdev/mxe/mxe_64b_20160617/tmp-default-octave/octave-4.1.0+/liboctave/wrappers/unistd-wrappers.h:74:8:
> error: 'pid_t' does not name a type
>  extern pid_t octave_getppid_wrapper (void);
>         ^
> /home/philip/devel/octdev/mxe/mxe_64b_20160617/tmp-default-octave/octave-4.1.0+/liboctave/wrappers/unistd-wrappers.h:86:8:
> error: 'pid_t' does not name a type
>  extern pid_t octave_setsid_wrapper (void);
>         ^
> /home/philip/devel/octdev/mxe/mxe_64b_20160617/tmp-default-octave/octave-4.1.0+/liboctave/wrappers/unistd-wrappers.h:96:8:
> error: 'pid_t' does not name a type
>  extern pid_t octave_vfork_wrapper (void);
>         ^
> 
> That octave-dev tip has been built fine & runs fine on Linux.
> 
> Anyone seen this too?

This is a very recent (within the last 24 hours) work in progress, so
you are on the front lines. Help us find and fix all compilation errors
with the recent changes on the default branch please.

-- 
mike



reply via email to

[Prev in Thread] Current Thread [Next in Thread]