X-Recipient: archive-cygwin@delorie.com X-SWARE-Spam-Status: No, hits=-50.9 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE X-Spam-Check-By: sourceware.org Subject: Re: Need swig 1.3.40 for Subversion From: "Yaakov (Cygwin/X)" To: cygwin In-Reply-To: <4C1FD3E8.50308@acm.org> References: <4C1FD3E8.50308@acm.org> Content-Type: text/plain; charset="UTF-8" Date: Tue, 22 Jun 2010 21:30:03 -0500 Message-ID: <1277260203.5496.36.camel@YAAKOV04> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com 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: ftp://sourceware.org/pub/cygwinports/uploads/swig/ Yaakov -- 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