OK, I've looked at it and I'm sorry to say I don't think this is the
right patch.
It seems to me that the patch disables gpgme.i's "const char *" typemap
definition by using
SWIG's bug of not reporting invalid syntax but silently ignoring it to
work around another SWIG
bug of the typemap causi
Sorry, I'm on LinuxWorld Expo this week and won't be able to look at
this until next week. If this switch appears just in 1.3.28 swig then
the change should be a little bit bigger for back compatibility.
Shortly, I greatly appreciate the patch - it gives me the right
direction where I need to l
Hello,
This bug [0] is due to swig upgrade. Actually, pyme builds fine with
swig < 1.3.28. In swig 1.3.28, there is a new option, namely 'match',
for typemaps.
I have attached the patch which fixes this bug. I have built and tested
pyme successfully using this patch. Could you please mak
Package: pyme
Version: 0.7.0-1
Severity: serious
Your package fails to build in unstable:
> Automatic build of pyme_0.7.0-1 on bigsur by sbuild/mips 1.106
...
> gcc -pthread -fno-strict-aliasing -DNDEBUG -g -O3 -Wall -Wstrict-prototypes
> -fPIC -I/build/tbm/pyme-0.7.0 -I/usr/include/python2.3 -c
4 matches
Mail list logo
