[M3devel] building m3gdb on AMD64_LINUX
Mika Nystrom
mika at async.caltech.edu
Sat Jul 4 19:21:11 CEST 2009
I guarantee that this "yacc" is not a faithful yacc.
"k" is the first initial of Karl Papadantonakis, the caltech-parser
package's author.
Mika
Jay writes:
>--_682f6248-704f-461d-9237-1a192e95b6fb_
>Content-Type: text/plain; charset="iso-8859-1"
>Content-Transfer-Encoding: quoted-printable
>
>
>It built ok for me a second time.
>
>The second time I removed /usr/local/cm3/bin from $PATH and deleted and re-=
>cvs-uped m3-sys/m3gdb.
>
>=20
>
>yacc comes from C:\dev2\cm3.2\caltech-parser\parserlib\kyacc\src.
>
>=20
>
>As long as nothing depend on running it by that name=2C and assuming it isn=
>'t a faithful replacement for other Yacc's=2C probably should rename it m3y=
>acc=2C or kyacc=2C whatever that means.
>
>=20
>
>You might just try rm -rf m3gdb and cvs -z3 upd -dAP.
>
>Maybe there is/was a timestamp problem.
>
>As Rodney said=2C it shouldn't need to run yacc=2C even if your yacc is mes=
>sed up.
>
>=20
>
> - Jay
>
>=20
>
>
>From: jay.krell at cornell.edu
>To: rodney.m.bates at cox.net=3B m3devel at elegosoft.com
>Date: Sat=2C 4 Jul 2009 15:28:24 +0000
>Subject: Re: [M3devel] building m3gdb on AMD64_LINUX
>
>
>
>It built ok for me=2C but there is a suspicous /usr/local/cm3/bin/yacc.
>I'm investigating more=2C but maybe not right now.
>=20
> - Jay
>
>=20
>> Date: Fri=2C 3 Jul 2009 16:53:31 -0500
>> From: rodney.m.bates at cox.net
>> To: m3devel at elegosoft.com
>> Subject: Re: [M3devel] building m3gdb on AMD64_LINUX
>>=20
>> On my AMD64_LINUX machine (Ubuntu 8.04.2)=2C on which m3gdb builds=2C yac=
>c
>> is circuitously symlinked to a script that executes /usr/bin/bison -y.
>>=20
>> In any case=2C usually=2C there is no need to execute yacc when building=
>=20
>> (m3)gdb=2C
>> because its output is already present and newer than yacc's input=2C in=20
>> this case=2C
>> c-exp.y. I think this is the way it is in the CVS repository. Did some=20
>> dates
>> in your source copy get touched?
>>=20
>> I have no idea where the c-exp.t file it wants is supposed to come from.
>> In a brief look=2C I didn't find any reference to a *.t file at all=2C=20
>> either in the script
>> m3gdb/gdb/ylwrap=2C nor in the yacc man page (which actually leads to the
>> bison man page on my machine). Maybe original yacc does something=20
>> with it.=20
>> I would have thought ylwrap would have been written to work with a number
>> of varieties of yacc and equivalents.=20
>>=20
>> Do you have a copy of c-exp.y?
>>=20
>> I suspect having a newer c-exp.c than c-exp.y will circumvent this=20
>> problem=2C but
>> of course we probably want it set up to work when c-exp.c needs to be=20
>> rebuilt.
>>=20
>> Olaf Wagner wrote:
>> > building m3gdb on birch ends with
>> >
>> > gcc -c -g -I. -I../../gdb/gdb -I../../gdb/gdb/config=20
>> > -DLOCALEDIR=3D"\"/usr/local/share/locale\"" -DHAVE_CONFIG_H=20
>> > -I../../gdb/gdb/../include/opcode -I../../gdb/gdb/../readline/..=20
>> > -I../bfd -I../../gdb/gdb/../bfd -I../../gdb/gdb/../include -I../intl=20
>> > -I../../gdb/gdb/../intl -DMI_OUT=3D1 -DTUI=3D1 -Wimplicit -Wreturn-type=
>=20
>> > -Wcomment -Wtrigraphs -Wformat -Wparentheses -Wpointer-arith=20
>> > -Wformat-nonliteral -Wunused-label -Wunused-function=20
>> > ../../gdb/gdb/tui/tui-winsource.c
>> > /bin/sh ../../gdb/gdb/../ylwrap ../../gdb/gdb/c-exp.y y.tab.c=20
>> > c-exp.c.tmp -- yacc
>> > Cannot open=20
>> > "/home/wagner/work/cm3/m3-sys/m3gdb/AMD64_LINUX/gdb/../../gdb/gdb/c-exp=
>.t"=20
>> >
>> > make[2]: *** [c-exp.c] Error 1
>> > make[2]: Leaving directory=20
>> > `/home/wagner/work/cm3/m3-sys/m3gdb/AMD64_LINUX/gdb'
>> > make[1]: *** [all-gdb] Error 2
>> > make[1]: Leaving directory=20
>> > `/home/wagner/work/cm3/m3-sys/m3gdb/AMD64_LINUX'
>> > make: *** [all] Error 2
>> > "/home/wagner/work/cm3/m3-sys/m3gdb/src/m3makefile"=2C line 121: quake=
>=20
>> > runtime error: exit 2: make CC=3D"gcc" CFLAGS=3D"-g" MAKEINFO=3Decho
>> >
>> > --procedure-- -line- -file---
>> > exec -- <builtin>
>> > m3gdb_Run 121 /home/wagner/work/cm3/m3-sys/m3gdb/src/m3makefile
>> > include_dir 160 /home/wagner/work/cm3/m3-sys/m3gdb/src/m3makefile
>> > 4=20
>> > /home/wagner/work/cm3/m3-sys/m3gdb/AMD64_LINUX/m3make.args
>> >
>> > Fatal Error: package build failed
>> >
>> > Any hints? Wrong yacc?
>> >
>> > Olaf
>>=20
>
>--_682f6248-704f-461d-9237-1a192e95b6fb_
>Content-Type: text/html; charset="iso-8859-1"
>Content-Transfer-Encoding: quoted-printable
>
><html>
><head>
><style>
>.hmmessage P
>{
>margin:0px=3B
>padding:0px
>}
>body.hmmessage
>{
>font-size: 10pt=3B
>font-family:Verdana
>}
></style>
></head>
><body class=3D'hmmessage'>
>It built ok for me a second time.<BR>
>The =3Bsecond time I removed /usr/local/cm3/bin from =3B$PATH and d=
>eleted and re-cvs-uped m3-sys/m3gdb.<BR>
> =3B<BR>
>yacc =3Bcomes from C:\dev2\cm3.2\caltech-parser\parserlib\kyacc\src.<BR=
>>
> =3B<BR>
>As long as nothing depend on running it by that name=2C and assuming it isn=
>'t a faithful =3Breplacement for other Yacc's=2C probably should rename=
> it m3yacc=2C or kyacc=2C whatever that means.<BR>
> =3B<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=2C it shouldn't need to run yacc=2C even if your yacc is mes=
>sed up.<BR>
> =3B<BR>
> =3B - Jay<BR><BR> =3B<BR>
><HR id=3DstopSpelling>
>From: jay.krell at cornell.edu<BR>To: rodney.m.bates at cox.net=3B m3devel at elegos=
>oft.com<BR>Date: Sat=2C 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=3B}
>.ExternalClass body.EC_hmmessage
>{font-size:10pt=3Bfont-family:Verdana=3B}
></STYLE>
>It built ok for me=2C but there is a =3Bsuspicous /usr/local/cm3/bin/ya=
>cc.<BR>I'm =3Binvestigating more=2C but =3Bmaybe not right now.<BR>=
> =3B<BR> =3B- Jay<BR><BR> =3B<BR>>=3B Date: Fri=2C 3 Jul 2009=
> 16:53:31 -0500<BR>>=3B From: rodney.m.bates at cox.net<BR>>=3B To: m3deve=
>l at elegosoft.com<BR>>=3B Subject: Re: [M3devel] building m3gdb on AMD64_LI=
>NUX<BR>>=3B <BR>>=3B On my AMD64_LINUX machine (Ubuntu 8.04.2)=2C on wh=
>ich m3gdb builds=2C yacc<BR>>=3B is circuitously symlinked to a script th=
>at executes /usr/bin/bison -y.<BR>>=3B <BR>>=3B In any case=2C usually=
>=2C there is no need to execute yacc when building <BR>>=3B (m3)gdb=2C<BR=
>>>=3B because its output is already present and newer than yacc's input=
>=2C in <BR>>=3B this case=2C<BR>>=3B c-exp.y. I think this is the way i=
>t is in the CVS repository. Did some <BR>>=3B dates<BR>>=3B in your sou=
>rce copy get touched?<BR>>=3B <BR>>=3B I have no idea where the c-exp.t=
> file it wants is supposed to come from.<BR>>=3B In a brief look=2C I did=
>n't find any reference to a *.t file at all=2C <BR>>=3B either in the scr=
>ipt<BR>>=3B m3gdb/gdb/ylwrap=2C nor in the yacc man page (which actually =
>leads to the<BR>>=3B bison man page on my machine). Maybe original yacc d=
>oes something <BR>>=3B with it. <BR>>=3B I would have thought ylwrap wo=
>uld have been written to work with a number<BR>>=3B of varieties of yacc =
>and equivalents. <BR>>=3B <BR>>=3B Do you have a copy of c-exp.y?<BR>&g=
>t=3B <BR>>=3B I suspect having a newer c-exp.c than c-exp.y will circumve=
>nt this <BR>>=3B problem=2C but<BR>>=3B of course we probably want it s=
>et up to work when c-exp.c needs to be <BR>>=3B rebuilt.<BR>>=3B <BR>&g=
>t=3B Olaf Wagner wrote:<BR>>=3B >=3B building m3gdb on birch ends with<=
>BR>>=3B >=3B<BR>>=3B >=3B gcc -c -g -I. -I../../gdb/gdb -I../../gdb=
>/gdb/config <BR>>=3B >=3B -DLOCALEDIR=3D"\"/usr/local/share/locale\"" -=
>DHAVE_CONFIG_H <BR>>=3B >=3B -I../../gdb/gdb/../include/opcode -I../../=
>gdb/gdb/../readline/.. <BR>>=3B >=3B -I../bfd -I../../gdb/gdb/../bfd -I=
>../../gdb/gdb/../include -I../intl <BR>>=3B >=3B -I../../gdb/gdb/../int=
>l -DMI_OUT=3D1 -DTUI=3D1 -Wimplicit -Wreturn-type <BR>>=3B >=3B -Wcomme=
>nt -Wtrigraphs -Wformat -Wparentheses -Wpointer-arith <BR>>=3B >=3B -Wf=
>ormat-nonliteral -Wunused-label -Wunused-function <BR>>=3B >=3B ../../g=
>db/gdb/tui/tui-winsource.c<BR>>=3B >=3B /bin/sh ../../gdb/gdb/../ylwrap=
> ../../gdb/gdb/c-exp.y y.tab.c <BR>>=3B >=3B c-exp.c.tmp -- yacc<BR>>=
>=3B >=3B Cannot open <BR>>=3B >=3B "/home/wagner/work/cm3/m3-sys/m3gd=
>b/AMD64_LINUX/gdb/../../gdb/gdb/c-exp.t" <BR>>=3B >=3B<BR>>=3B >=3B=
> make[2]: *** [c-exp.c] Error 1<BR>>=3B >=3B make[2]: Leaving directory=
> <BR>>=3B >=3B `/home/wagner/work/cm3/m3-sys/m3gdb/AMD64_LINUX/gdb'<BR>=
>>=3B >=3B make[1]: *** [all-gdb] Error 2<BR>>=3B >=3B make[1]: Leav=
>ing directory <BR>>=3B >=3B `/home/wagner/work/cm3/m3-sys/m3gdb/AMD64_L=
>INUX'<BR>>=3B >=3B make: *** [all] Error 2<BR>>=3B >=3B "/home/wagn=
>er/work/cm3/m3-sys/m3gdb/src/m3makefile"=2C line 121: quake <BR>>=3B >=
>=3B runtime error: exit 2: make CC=3D"gcc" CFLAGS=3D"-g" MAKEINFO=3Decho<BR=
>>>=3B >=3B<BR>>=3B >=3B --procedure-- -line- -file---<BR>>=3B >=
>=3B exec -- <=3Bbuiltin>=3B<BR>>=3B >=3B m3gdb_Run 121 /home/wagner=
>/work/cm3/m3-sys/m3gdb/src/m3makefile<BR>>=3B >=3B include_dir 160 /hom=
>e/wagner/work/cm3/m3-sys/m3gdb/src/m3makefile<BR>>=3B >=3B 4 <BR>>=3B=
> >=3B /home/wagner/work/cm3/m3-sys/m3gdb/AMD64_LINUX/m3make.args<BR>>=
>=3B >=3B<BR>>=3B >=3B Fatal Error: package build failed<BR>>=3B >=
>=3B<BR>>=3B >=3B Any hints? Wrong yacc?<BR>>=3B >=3B<BR>>=3B >=
>=3B Olaf<BR>>=3B <BR></body>
></html>=
>
>--_682f6248-704f-461d-9237-1a192e95b6fb_--
More information about the M3devel
mailing list