Date: Wed, 22 Mar 2000 11:14:15 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Ultan Henry <ultan AT cix DOT compulink DOT co DOT uk>
cc: djgpp AT delorie DOT com
Subject: Re: Binutils 2.9.5.1 Cross-Compile
In-Reply-To: <memo.683641@cix.compulink.co.uk>
Message-ID: <Pine.SUN.3.91.1000322111344.17945d@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp AT delorie DOT com
Errors-To: dj-admin AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Tue, 21 Mar 2000, Ultan Henry wrote:

> C:/DJGPP/BIN/sh.exe ./../ylwrap "bison -y" ./itbl-parse.y y.tab.c 
> itbl-parse.c y.tab.h itbl-parse.h -- -d
> c:/djgpp/bin/bison.exe: itbl-parse.y: No such file or directory (ENOENT)

What happens if you invoke this exact command line manually, from the
same directory `c:/temp/gnu/binutl-2.951/gas'?

Also, what version of Bison do you use?

> Any ideas what is wrong?

Note that Bison is invoked here via a wrapper script ylwrap.  One idea
is to look inside that script and see how does it invoke Bison.  For
example, perhaps it chdirs to some directory before running Bison, and
fails to convert itbl-parse.y to an absolute file name (especially if
the other directory is on another drive).