Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm 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 Message-Id: <5.1.0.14.0.20031117114125.00a08140@pop.mail.yahoo.co.uk> X-Sender: ian_badcoe AT pop DOT mail DOT yahoo DOT co DOT uk Date: Mon, 17 Nov 2003 11:48:30 +0000 To: cygwin AT cygwin DOT com From: Ian Badcoe Subject: Building bison? In-Reply-To: References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Hi, This may well verge on FAQ-like issues, but a quick search didn't find it. I've been investigating a possible bug in bison, and talking with the folk on the bison-bug mail-list. Fairly reasonably, their first request was that I build their latest version and see if the bug still occurs. An they gave me a version numbered 1.875c (the current cygwin version is 1.975b, so they are pretty similar). 1.875c behaves nicely to a ./configure and make but it then crashes immediately when I give it my input script. I was wondering whether I should have expected that, or whether packages generally get patched when converted to cygwin? I ask because I seem re recall some posts on this list a few months ago, which were about how much needed patching, every time new sources where brought over from GNU? So, are any special actions required when getting source from other places than via the cygwin setup program? Ian B Free transport into the future, while you wait. -- 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/