|
From: | John Donoghue |
Subject: | Re: MXE compile and popen2 |
Date: | Sat, 21 May 2016 19:33:34 -0400 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.0 |
On 05/21/2016 01:08 PM, John Donoghue
wrote:
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
I can get past that error by defining a typedef of the function and using that as: +typedef pid_t (*popen_func)(const std::string&, const
string_vector&,
However next error occurs with the octave::sys::popen2 being defined twice: liboctave/system/lo-sysdep.cc
|
[Prev in Thread] | Current Thread | [Next in Thread] |