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
Message-ID: <00ed01c39325$0d269050$5222a8c0@windows.micromuse.com>
From: "Daniel Edwards" <ded AT micromuse DOT com>
To: <cygwin AT cygwin DOT com>
Subject: 'bison' error, possibly installation related
Date: Wed, 15 Oct 2003 15:02:58 +0100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165

Hello,

I'm getting the following error when i'm running the following bison command

bison -yd -r all -p _NPropMgr prop_parser.y

Signal 6
*** Error code 134


However, I've recently moved the cygwin installation and remounted and I
think this is the real problem as I can make the problem go away if i
recreate a cygwin installation from scratch, but the environment i'm working
in isn't going to be able to support that.

I need to know more about the error so that i can resolve it.  I've been
unable to find out anything so far.  I'm assuming that Signal 6 is sigalrm.
I'd like to know how i could find out more about error code 134, or what
bison is struggling with that causes this issue.

thanks

dan


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