Re: [Bug-gnubg] Is anyone else seeing ylwrap problems building gnubg?

[Jim Segrave]

On Mon 07 Jun 2004 (19:57 +0200), Holger wrote:
> At 08:22 03.06.2004, Jim Segrave wrote:
> >On Tue 01 Jun 2004 (08:38 +0100), Jon Kinsey wrote:
> >> Jim Segrave wrote:
> >>
> >> >I just got a new laptop and, after getting FreeBSD and X up and
> >> >running, I went to build gnubg from CVS. When I tried, the make failed
> >> >on external_y.c:
> >> >
> >> >after building timer.o:
> >> >/usr/local/bin/bash ./ylwrap `test -f 'external_y.y' || echo
> >> >'./'`external_y.y y .tab.c external_y.c y.tab.h external_y.h
> >> >y.output external_y.output -- bison -y  -d
> >> >gmake[2]: *** [external_y.c] Error 1
> 
> I've got the same problem here on Solaris 9 (finally tried it again). Fresh 
> CVS checkout.
> 
> >> You can check it's this by removing the following line from external_y.y:
> >> %output="external_y.c"
> >
> >Yes - that fixes it. I suppose we should do this, but I'm not
> >sure. ylwrap is an ugly hack, but if some people are building gnubg on
> >a system without a gnu toolchain, this will introduce problems.
> 
> Without the line  >> %output="external_y.c" << in external_y.y I get:
> 
> /bin/bash ./ylwrap `test -f 'external_l.l' || echo './'`external_l.l 
> lex.yy.c external_l.c -- flex
> gmake[2]: *** [external_l.c] Error 1
> 
> Regards,
> 
>         Holger 

Try putting a line

set -x 

in the top of ylwrap and somewhere near the bottom, comment out the rm
of the directory. Then when it fails, you can see what the script was
up to and you can see the contents of the directory where the y.tab.c
and similar files should be, In fact, you can run ylwrap by hand by
copying what make reports when it runs.


-- 
Jim Segrave           address@hidden