Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Subject: RE: Building bison?
Date: Tue, 18 Nov 2003 08:38:38 +0100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Message-ID: <F0D7281DAB048B438E8F5EC4ECEFBDDC175F92@esmail.elsag.de>
X-MS-Has-Attach: 
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
X-MS-TNEF-Correlator: 
content-class: urn:content-classes:message
From: =?iso-8859-1?Q?J=F6rg_Schaible?= <Joerg DOT Schaible AT Elsag-Solutions DOT com>
To: <cygwin AT cygwin DOT com>
Cc: "Ian Badcoe" <ian_badcoe AT yahoo DOT co DOT uk>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id hAI7cs93032188

Ian,

please stay on the list for ongoing conversation ...

Ian Badcoe wrote on Monday, November 17, 2003 9:27 PM:
> At 14:40 17/11/2003 +0100, you wrote:
>> Ian Badcoe wrote on Monday, November 17, 2003 12:49 PM:
>> [snip]
>>>       1.875c behaves nicely to a ./configure and make but it then
>>> crashes immediately when I give it my input script.
>> 
>> Just an idea: Since Cygwin compiles as Unix flavour, the original
>> source may not be prepared to read files with CRLF. Try to run it
>> from a binary mounted folder providing a file with LF endings only.
> 
> If I invoke bison indirectly:
>          bash -c "/usr/bin/bison MyFile.y ..."
> 
> Then it works, so I suspect it's more to do with invocation than CRLF.

What is the value of your CYGWIN enrironment variable?

> As a general question, is there generally a lot of difference between
> sources downloaded from GNU and one's acquired via cygwin?
> Or can one mix
> and match freely (bugs due to version differences notwithstanding)?

Changes for a package are normally documented in /usr/doc/Cygwin. 

Regards,
Jörg

--
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/