Message: 1
Date: Fri, 20 May 2016 16:14:05 -0400
From: "John W. Eaton" <address@hidden>
To: address@hidden
Cc: address@hidden
Subject: Re: MXE compile and popen2
Message-ID: <address@hidden>
Content-Type: text/plain; charset=windows-1252; format=flowed
On 05/20/2016 04:03 PM, JohnD wrote:
> Using const auto octave_popen2 = &octave::sys::popen2; (note the
> ampersand) appears to be compiling ok. Not tested yet for it runs though.
Hmm. Is this only failing for popen2? What about the other symbols
that are defined this way? Do you not see warnings from the definition
of octave_chdir and octave_getcwd that are also defined in lo-sysdep.h?
jwe
It is only for popen - I think the error is misleading, and it is
really an issue with not knowing pid_t from within that file.