X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Wed, 28 May 2008 22:01:30 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: binutils 20080523-1: version string breaks python2.5 distutils Message-ID: <20080529020130.GA13665@ednor.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <20080528 DOT 214955 DOT 28844 DOT 0 AT webmail21 DOT dca DOT untd DOT com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20080528.214955.28844.0@webmail21.dca.untd.com> User-Agent: Mutt/1.5.16 (2007-06-09) Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com On Thu, May 29, 2008 at 01:49:55AM +0000, Joe Pham wrote: >As part of the binutils 20080523-1 package, both ld (ld -v) and dllwrap >(dllwrap --version) report their version as "2.18.50.20080523". This >version string format causes the python2.5 distutils tool to abort with >error. On Linux, the format would have been something like "2.18.50 >20080523". Any chance to make this consistent with Linux? The version string is straight from a standard binutils distribution. Nothing has been done to modify it. It comes from this line in the bfd Makefile: ./bfd/Makefile: bfd_version_string="\"$(VERSION).$${bfd_version_date}\"" ;\ So, no. I'd suggest modifying python. It pretty clearly doesn't adapt correctly to a standard binutils version string. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/