Thanks for info Ian,
I assume you're using Python 3.7, which changed the return type of
`PyUnicode_AsUTF8` from `char*` to `const char*`. I've fixed this in PR
456: https://github.com/stevengj/meep/pull/456
Chris
On Tue, Aug 7, 2018 at 4:59 AM, Ian Sage <i...@sage.myzen.co.uk> wrote:
> On Arch linux, installing from git through the AUR packages, I now see a
> problem reminiscent of (but different from) John's:
>
> In file included from meep-python.cpp:3794:
> typemap_utils.cpp: In function ‘std::__cxx11::string
> py_class_name_as_string(PyObject*)’:
> typemap_utils.cpp:21:51: error: invalid conversion from ‘const char*’ to
> ‘char*’ [-fpermissive]
> #define PyObject_ToCharPtr(n) PyUnicode_AsUTF8(n)
> ~~~~~~~~~~~~~~~~^~~
> This follows an update of harminv, libctl, h5utils, mpb without problems,
> motivated by a compiler libraries update.
>
> Any clues?
>
> Many thanks,
>
> Ian
> On 02/08/18 06:24, John Weiner wrote:
>
> Meep.hpp:1275:78 error: invalid conversion from ‘meep::component*’ to
> ‘int’ -fpermissive:
> chunk loop filed components (fc, grid, shift, phase, S, sh,
> components.data(), components.size()) {}
>
>
>
>
> _______________________________________________
> meep-discuss mailing list
> meep-discuss@ab-initio.mit.edu
> http://ab-initio.mit.edu/cgi-bin/mailman/listinfo/meep-discuss
>
_______________________________________________
meep-discuss mailing list
meep-discuss@ab-initio.mit.edu
http://ab-initio.mit.edu/cgi-bin/mailman/listinfo/meep-discuss
