Read and respond to this message at:
I tried to recompile the binutils cross (--target=i686-linux and some 12 other
architecture-platform combinations), I fail each time with the ylwrap script.
First it seemed to nag about the -d parameter, but that could be the fact that
I had no lex or yacc. So I tried installing bison but that failed. 2.13 or 2.14
didn't matter. ( I used the binutils-xx.yy.sh script btw, so
my configure params should be good, only changed the target)
Does somebody have a step to step guide to create a minimal build to generate
I installed mingw runtime, utils, gcc-core, binutils (bin and source), win32api
mingw make and msys (core pkg) and msys-devel and bison
You are receiving this email because you elected to monitor this forum.
To stop monitoring this forum, login to SourceForge.net and visit:
From: Chris Johns <cjohns@cy...> - 2003-10-06 01:51:48
> Does somebody have a step to step guide to create a minimal build to generate
I hit the same problem with gdb and found the problem is related to the
way windows copies files, and/or make's time check, and/or load on the
mcahine. Repeated coping of original sources to a copy to patch
sometimes triggered the need for yacc to run. The configure script
detects no yacc but does not fail (nor should it). As a result $(YACC)
in the makefile results in "" on the command line to ylwrap and sh
generates strange messages.
The simple solution is find the source generated by yacc and touch them.
For gdb this is:
$ touch gdb/*.tab.c
Chris Johns, cjohns at cybertec.com.au