octave-maintainers
[Top][All Lists]
Advanced

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

MXE win32 errors "'WIFEXITED' was not declared in this scope"


From: John D
Subject: MXE win32 errors "'WIFEXITED' was not declared in this scope"
Date: Thu, 26 Jun 2014 09:21:38 -0400

They  do not appear to be defined for mingw, and the system function for
mingw/win32 returns just the program return value, or -1 in error.

http://msdn.microsoft.com/en-us/library/277bwbdz%28v=VS.100%29.aspx


-------------------------
Message: 4
Date: Wed, 25 Jun 2014 11:11:16 -0700 (PDT)
From: Philip Nienhuis <address@hidden>
To: address@hidden
Subject: MXE win32 errors "'WIFEXITED' was not declared in this scope"
Message-ID: <address@hidden>
Content-Type: text/plain; charset=us-ascii

When trying to build octave-4.1.0+ for windows (MXE-cross-build) I get error
messages related to mkoctfile, apparently due to changeset 5b7b18d603ae
'mkoctfile.in.cc: fix return value if subprocess fails (bug #42549).':

mkoctfile.cc:348:24: error 'WIFEXITED' was not declared in this scope

mkoctfile.cc:349:33: error 'WEXITSTATUS' was not declared in this scope

Where are these identifiers (macros) declared for win32 systems?

See threads in the maintainers ML mentioned in the bugreport (#42549):
http://octave.1599824.n4.nabble.com/mkoctfile-exits-with-0-if-gcc-failed-td4
664462.html
http://octave.1599824.n4.nabble.com/RE-return-code-of-mkoctfile-td4664466.ht
ml

Thanks,

Philip







reply via email to

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