On 6/22/2010 7:30 PM, Yaakov (Cygwin/X) wrote:
> On Mon, 2010-06-21 at 14:04 -0700, David Rothenberger wrote:
>> It seems that swig-1.3.38 has a bug that produces invalid Python
>> bindings with Python 2.6. I first hit this when building
>> subversion-1.6.11-2 for Python 2.6, but I dismissed the test case
>> failures at the time.
>>
>> Today I built subversion-1.6.12-1 and took the time to investigate. The
>> Python bindings won't run when generated with swig 1.3.38 but run fine
>> when generated with 1.3.40.
>>
>> Therefore, I respectively request that the swig maintainer update swig
>> to 1.3.40. (I believe swig 2.0.0 was just release, but I have no idea if
>> Subversion will build with that version.)
>
> Would you mind trying with 2.0.0? I uploaded a package here:
It doesn't build with swig 2.0.0 and I don't have time to investigate
why. The swig bindings are generated fine, but they don't compile.
--
David Rothenberger ---- daver...@acm.org
"Nuclear war would really set back cable."
-- Ted Turner
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
