Re: Building PyTave on windows - cygwin

[Tatsuro MATSUOKA]

----- Original Message -----

> From: Mike Miller 
> To: Abhinav Tripathi 
> Cc: Tatsuro MATSUOKA ; "Octave-maintainers
> Date: 2016/6/17, Fri 14:42
> Subject: Re: Building PyTave on windows - cygwin
> 
> On Fri, Jun 17, 2016 at 09:55:56 +0530, Abhinav Tripathi wrote:
>>   I did that I the build went a little further. It now gives these errors in
>>  octave headers:
>>  ----------------------------------------------------------
>>  pycall.o: In function `Gpycall':
>>  E:\My_Repos\pytave/pycall.cc:40: undefined reference to 
> `check_version(std::__cxx11::basic_string<char, std::char_traits<char>, 
> std::allocator<char> > const&, std::__cxx11::basic_string<char, 
> std::char_traits<char>, std::allocator<char> > const&)'
> […]
>>  I don't know if it is a c++11 compatiblity error or due to missing lib
>>  files...
> 
> Looks like the C++11 ABI transition incompatibility. Around gcc 5, a
> change in the library ABI was done, see
> 
>   https://gcc.gnu.org/onlinedocs/libstdc++/manual/using_dual_abi.html
> 
> My guess is Octave was built with the legacy pre-C++11 ABI, but pytave
> is being built with the new ABI.
> 
> Did your msys development setup pull in a different version of gcc than
> the one that Octave's installer comes with?
> 
> -- 
> mike


Ah! 

Abhinav seems to use gcc-5.4.0 mingw 64 on msys2.
The version gcc on octave for windows is 4.9.3.

This may cause conflicts.

Possible workaround is

CC='/e/octave_dev/bin/gcc' \
CXX='/e/octave_dev/bin/g++' \
F77='/e/octave_dev/bin/gfortran' \
CPPFLAGS='(proper setting)' \
LFLAGS='(proper setteing)' \
./configure

You might need other libraries like python and boost using gcc embedded on 
octave.

Tatsuro