<html>
<head>
<style>
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Verdana
}
</style>
</head>
<body class='hmmessage'>
See also C:\dev2\cm3.2\caltech-parser\parserlib\klex\src<BR><BR><BR><BR><BR> <BR>
<HR id=stopSpelling>
From: jay.krell@cornell.edu<BR>To: rodney.m.bates@cox.net; m3devel@elegosoft.com<BR>Subject: RE: [M3devel] building m3gdb on AMD64_LINUX<BR>Date: Sat, 4 Jul 2009 15:33:48 +0000<BR><BR>
<STYLE>
.ExternalClass .EC_hmmessage P
{padding:0px;}
.ExternalClass body.EC_hmmessage
{font-size:10pt;font-family:Verdana;}
</STYLE>
It built ok for me a second time.<BR>The second time I removed /usr/local/cm3/bin from $PATH and deleted and re-cvs-uped m3-sys/m3gdb.<BR> <BR>yacc comes from C:\dev2\cm3.2\caltech-parser\parserlib\kyacc\src.<BR> <BR>As long as nothing depend on running it by that name, and assuming it isn't a faithful replacement for other Yacc's, probably should rename it m3yacc, or kyacc, whatever that means.<BR> <BR>You might just try rm -rf m3gdb and cvs -z3 upd -dAP.<BR>Maybe there is/was a timestamp problem.<BR>As Rodney said, it shouldn't need to run yacc, even if your yacc is messed up.<BR> <BR> - Jay<BR><BR> <BR>
<HR id=EC_stopSpelling>
From: jay.krell@cornell.edu<BR>To: rodney.m.bates@cox.net; m3devel@elegosoft.com<BR>Date: Sat, 4 Jul 2009 15:28:24 +0000<BR>Subject: Re: [M3devel] building m3gdb on AMD64_LINUX<BR><BR>
<STYLE>
.ExternalClass .EC_hmmessage P
{padding:0px;}
.ExternalClass body.EC_hmmessage
{font-size:10pt;font-family:Verdana;}
</STYLE>
It built ok for me, but there is a suspicous /usr/local/cm3/bin/yacc.<BR>I'm investigating more, but maybe not right now.<BR> <BR> - Jay<BR><BR> <BR>> Date: Fri, 3 Jul 2009 16:53:31 -0500<BR>> From: rodney.m.bates@cox.net<BR>> To: m3devel@elegosoft.com<BR>> Subject: Re: [M3devel] building m3gdb on AMD64_LINUX<BR>> <BR>> On my AMD64_LINUX machine (Ubuntu 8.04.2), on which m3gdb builds, yacc<BR>> is circuitously symlinked to a script that executes /usr/bin/bison -y.<BR>> <BR>> In any case, usually, there is no need to execute yacc when building <BR>> (m3)gdb,<BR>> because its output is already present and newer than yacc's input, in <BR>> this case,<BR>> c-exp.y. I think this is the way it is in the CVS repository. Did some <BR>> dates<BR>> in your source copy get touched?<BR>> <BR>> I have no idea where the c-exp.t file it wants is supposed to come from.<BR>> In a brief look, I didn't find any reference to a *.t file at all, <BR>> either in the script<BR>> m3gdb/gdb/ylwrap, nor in the yacc man page (which actually leads to the<BR>> bison man page on my machine). Maybe original yacc does something <BR>> with it. <BR>> I would have thought ylwrap would have been written to work with a number<BR>> of varieties of yacc and equivalents. <BR>> <BR>> Do you have a copy of c-exp.y?<BR>> <BR>> I suspect having a newer c-exp.c than c-exp.y will circumvent this <BR>> problem, but<BR>> of course we probably want it set up to work when c-exp.c needs to be <BR>> rebuilt.<BR>> <BR>> Olaf Wagner wrote:<BR>> > building m3gdb on birch ends with<BR>> ><BR>> > gcc -c -g -I. -I../../gdb/gdb -I../../gdb/gdb/config <BR>> > -DLOCALEDIR="\"/usr/local/share/locale\"" -DHAVE_CONFIG_H <BR>> > -I../../gdb/gdb/../include/opcode -I../../gdb/gdb/../readline/.. <BR>> > -I../bfd -I../../gdb/gdb/../bfd -I../../gdb/gdb/../include -I../intl <BR>> > -I../../gdb/gdb/../intl -DMI_OUT=1 -DTUI=1 -Wimplicit -Wreturn-type <BR>> > -Wcomment -Wtrigraphs -Wformat -Wparentheses -Wpointer-arith <BR>> > -Wformat-nonliteral -Wunused-label -Wunused-function <BR>> > ../../gdb/gdb/tui/tui-winsource.c<BR>> > /bin/sh ../../gdb/gdb/../ylwrap ../../gdb/gdb/c-exp.y y.tab.c <BR>> > c-exp.c.tmp -- yacc<BR>> > Cannot open <BR>> > "/home/wagner/work/cm3/m3-sys/m3gdb/AMD64_LINUX/gdb/../../gdb/gdb/c-exp.t" <BR>> ><BR>> > make[2]: *** [c-exp.c] Error 1<BR>> > make[2]: Leaving directory <BR>> > `/home/wagner/work/cm3/m3-sys/m3gdb/AMD64_LINUX/gdb'<BR>> > make[1]: *** [all-gdb] Error 2<BR>> > make[1]: Leaving directory <BR>> > `/home/wagner/work/cm3/m3-sys/m3gdb/AMD64_LINUX'<BR>> > make: *** [all] Error 2<BR>> > "/home/wagner/work/cm3/m3-sys/m3gdb/src/m3makefile", line 121: quake <BR>> > runtime error: exit 2: make CC="gcc" CFLAGS="-g" MAKEINFO=echo<BR>> ><BR>> > --procedure-- -line- -file---<BR>> > exec -- <builtin><BR>> > m3gdb_Run 121 /home/wagner/work/cm3/m3-sys/m3gdb/src/m3makefile<BR>> > include_dir 160 /home/wagner/work/cm3/m3-sys/m3gdb/src/m3makefile<BR>> > 4 <BR>> > /home/wagner/work/cm3/m3-sys/m3gdb/AMD64_LINUX/m3make.args<BR>> ><BR>> > Fatal Error: package build failed<BR>> ><BR>> > Any hints? Wrong yacc?<BR>> ><BR>> > Olaf<BR>> <BR></body>
</html>