Any ideas how to make it working? Another problem is that I would need a
solution which works from swig 2.0.10 upwards as M2Crypto should be able
to be build and maintained on RHEL-7 as well. Any help?

Any ideas how to make it working? Another problem is that I would need a
solution which works from swig 2.0.10 upwards as M2Crypto should be able
to be build and maintained on RHEL-7 as well. Any help?

The maintainer of these interface files is probably the best person to ask. If you provide a cutdown instance of the problem to this list, we can take a look.

Re: Weirdly generated C code

On 2017-04-21, 07:16 GMT, William S Fulton wrote:

> On 10 April 2017 at 18:19, Matěj Cepl <[hidden email]> wrote:
>> when trying to build M2Crypto with swig 3.0.12 and gcc 7.0.1
>> 20170327 on
>> Fedora/Rawhide. Swig generates this C file
>> (plain C, not C++) https://mcepl.fedorapeople.org/tmp/_m2crypto_wrap.c.bz2>>
>> and when I try to build it with GCC I get the following errors (the full
>> log is at https://mcepl.fedorapeople.org/tmp/python-clean-build-log.txt ).
>>
>> Any ideas how to make it working? Another problem is that I would need a
>> solution which works from swig 2.0.10 upwards as M2Crypto should be able
>> to be build and maintained on RHEL-7 as well. Any help?
>>
>
> The maintainer of these interface files is probably the best person to ask.
> If you provide a cutdown instance of the problem to this list, we can take
> a look.

And who is this maintainer? When trying again, swig 3.0.12
generates these weird functions (example [1]), which break with
compilation. Can I somehow avoid generating of these functions
altogether?