This is the mail archive of the binutils@sourceware.cygnus.com mailing list for the binutils project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: patch for ylwrap


   From: "Mark E." <snowball3@bigfoot.com>
   Date: Fri, 11 Jun 1999 14:56:24 -0400

   > The patch lets ylwrap accept filenames without regard to the directory 
   > separator is used.

   I'm building for i386-pc-msdosdjgpp with a three day old version of 
   binutils from CVS.

   The first version of the patch didn't go far enough. Here's a revised 
   version:

ylwrap is provided by automake, so bugs in ylwrap should be reported
to bug-automake@gnu.org.

   However, even after correcting those, make still stops:

   C:/DJGPP/BIN/make.exe  all-recursive
   make.exe[1]: Entering directory `c:/djgpp/cvs/binutils/binutils'
   Making all in po
   make.exe[2]: Entering directory `c:/djgpp/cvs/binutils/binutils/po'
   make.exe[2]: Nothing to be done for `all'.
   make.exe[2]: Leaving directory `c:/djgpp/cvs/binutils/binutils/po'
   make.exe[2]: Entering directory `c:/djgpp/cvs/binutils/binutils'
   C:/DJGPP/BIN/sh.exe ./../ylwrap "`if [ -f ../bison/bison ] ; then echo 
   ../bison/bison -y -L./../bison/ ; else echo bison -y ; fi`" arparse.y y.tab.c 
   arparse.c y.tab.h arparse.h --  -d
   C:/DJGPP/BIN/bison.exe: arparse.y: No such file or directory (ENOENT)
   make.exe[2]: *** [arparse.c] Error 1
   make.exe[2]: Leaving directory `c:/djgpp/cvs/binutils/binutils'
   make.exe[1]: *** [all-recursive] Error 1
   make.exe[1]: Leaving directory `c:/djgpp/cvs/binutils/binutils'
   make.exe: *** [all-recursive-am] Error 2

   arparse.y is there, but somehow isn't being found. What's going on?

I dunno.  My first guess would be that it's some djgpp thing.  I think
that when you build in the source directory like this, ylwrap will
create a temporary directory, cd into it, and copy the input file
down.  Perhaps that copy step is failing for some reason.

The best way I know to debug a shell script is to run it with the -x
and perhaps also the -v option.  That is, cd into binutils, and run
something like

    C:/DJGPP/BIN/sh.exe -x ./../ylwrap "`if [ -f ../bison/bison ] ; then echo ../bison/bison -y -L./../bison/ ; else echo bison -y ; fi`" arparse.y y.tab.c arparse.c y.tab.h arparse.h --  -d

Ian

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]