From: asmwarrior <asmwarrior@gmail.com>
To: gdb@sourceware.org,
MinGW Users List <mingw-users@lists.sourceforge.net>
Subject: mingw bison error when building gdb git source
Date: Sat, 04 Jun 2011 12:49:00 -0000 [thread overview]
Message-ID: <4DEA2A05.5000903@gmail.com> (raw)
I have a question on building gdb under Msys+mingw
when I build gdb source from git (which I do a git clone from
git://sourceware.org/git/gdb.git). I get an build error:
-----------------------------------------------------------------
make[2]: Entering directory `/f/build_gdb/gdb/gdbgit/build/sim'
make[2]: Leaving directory `/f/build_gdb/gdb/gdbgit/build/sim'
make[2]: Entering directory `/f/build_gdb/gdb/gdbgit/build/gdb'
CONFIG_HEADERS=config.h:config.in \
CONFIG_COMMANDS="default depdir" \
CONFIG_FILES= \
CONFIG_LINKS= \
/bin/sh config.status
config.status: creating config.h
config.status: config.h is unchanged
config.status: executing default commands
config.status: executing depdir commands
rm -f c-exp.c c-exp.c.tmp
/bin/sh ../../gdb/gdb/../ylwrap ../../gdb/gdb/c-exp.y y.tab.c c-exp.c --
bison -
y && mv c-exp.c c-exp.c.tmp \
|| (rm -f c-exp.c; false)
rm -f cp-name-parser.c cp-name-parser.c.tmp
/bin/sh ../../gdb/gdb/../ylwrap ../../gdb/gdb/cp-name-parser.y y.tab.c
cp-name-p
arser.c -- bison -y && mv cp-name-parser.c cp-name-parser.c.tmp \
|| (rm -f cp-name-parser.c; false)
rm -f objc-exp.c objc-exp.c.tmp
/bin/sh ../../gdb/gdb/../ylwrap ../../gdb/gdb/objc-exp.y y.tab.c
objc-exp.c -- b
ison -y && mv objc-exp.c objc-exp.c.tmp \
|| (rm -f objc-exp.c; false)
conflicts: 18 shift/reduce, 9 reduce/reduce
E:\code\msys\MSYS-20110112\msys\bin\bison.exe: cannot open file
`/usr/share/biso
n/m4sugar/m4sugar.m4': No such file or directory
E:\code\msys\MSYS-20110112\msys\bin\bison.exe: cannot open file
`/usr/share/biso
n/m4sugar/m4sugar.m4': No such file or directory
conflicts: 5 shift/reduce
E:\code\msys\MSYS-20110112\msys\bin\bison.exe: cannot open file
`/usr/share/biso
n/m4sugar/m4sugar.m4': No such file or directory
make[2]: *** [c-exp.c] Error 1
make[2]: *** Waiting for unfinished jobs....
make[2]: *** [cp-name-parser.c] Error 1
make[2]: *** [objc-exp.c] Error 1
make[3]: Entering directory `/f/build_gdb/gdb/gdbgit/build/gdb'
make[4]: Entering directory `/f/build_gdb/gdb/gdbgit/build/gdb/gnulib'
make all-recursive
------------------------------------------------------------------------
The message shows that bison under Msys does not works quite well.
But when I download the gdb snapshot from the ftp
ftp://sourceware.org/pub/gdb/snapshots/
I just unzip the snapshot, and use the same configure option, and the
build stage works fine, and no such error.
So, I just think that when building the snapshot, we do not need bison.
In fact the file c-exp.c is built from c-exp.y.
In the snapshot of gdb, c-exp.y already exists.
But in the gdb git source, there are only c-exp.y, so bison is needed to
build the associated c-exp.c.
So, my question is:
Can some bison exports help to solve this problem? it seems bison under
Msys does not works quite well.
Or is it possible save the c-exp.c in the gdb repository, so that we
don't need bison to build it.
thanks.
asmwarrior
ollydbg from code::blocks' forum
next reply other threads:[~2011-06-04 12:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-04 12:49 asmwarrior [this message]
[not found] <4DEA2A05.5000903__6600.81413011557$1307191775$gmane$org@gmail.com>
2011-06-04 13:32 ` asmwarrior
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4DEA2A05.5000903@gmail.com \
--to=asmwarrior@gmail.com \
--cc=gdb@sourceware.org \
--cc=mingw-users@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).