Great detective work! Looks like there are multiple problems in the
current version and it's not clear what the "best" (upstream, ideally)
solution is. But also, it's a painful packaging situation (for fink) to
have one specific python-version's bindings in the same .info as the
library itself,
Thanks for the reply,
In addition I found the following reference on the web concerning the issue:
http://old.nabble.com/python-warning%3A-%27set%27-conflicts-with-a-built-in-name-td33960637.html
Regards,
Norbert
Am 11.05.2013 um 03:56 schrieb Alexander Hansen :
> On 5/10/13 9:00 AM, Norbert Kl
On 5/10/13 9:00 AM, Norbert Klisch wrote:
> Hi,
>
> I get an make error for libopensync1-shlibs-0.39-3 and afterwards
> make stops:
>
> /sw/src/fink.build/libopensync1-shlibs-0.39-3/libopensync-0.39/wrapper/opensync-error.i:51:
> Warning 321: 'set' conflicts with a built-in name in python
> make[2]
Hi,
I get an make error for libopensync1-shlibs-0.39-3 and afterwards make stops:
/sw/src/fink.build/libopensync1-shlibs-0.39-3/libopensync-0.39/wrapper/opensync-error.i:51:
Warning 321: 'set' conflicts with a built-in name in python
make[2]: *** [wrapper/opensyncPYTHON_wrap.c] Error 1
make[1]:
Hi,
I get an make error for libopensync1-shlibs-0.39-3 and afterwards make stops:
/sw/src/fink.build/libopensync1-shlibs-0.39-3/libopensync-0.39/wrapper/opensync-error.i:51:
Warning 321: 'set' conflicts with a built-in name in python
make[2]: *** [wrapper/opensyncPYTHON_wrap.c] Error 1
make[1]:
