Hello.
I ran into another problem.
gcc -g -DIN_GCC -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -pedantic -Wno-long-long -fno-common -DHAVE_CONFIG_H -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -pedantic -Wno-long-long -fno-common -pedantic -Wno-long-long -o xgpc p/gpc.o prefix.o version.o \ intl.o ../libiberty/libiberty.a gcc -o p/diagnostic.o -c -g -DIN_GCC -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -fno-common -DHAVE_CONFIG_H -I. -Ip -I../../gcc-3.4-20040702/gcc -I../../gcc-3.4-20040702/gcc/p -I../../gcc-3.4-20040702/gcc/../include -DGPC ../../gcc-3.4-20040702/gcc/diagnostic.c echo "expect 16 shift/reduce and 30 reduce/reduce conflicts" >&2 expect 16 shift/reduce and 30 reduce/reduce conflicts cd ../../gcc-3.4-20040702/gcc/p && bison -o parse.c parse.y parse.y: conflicts: 16 shift/reduce, 295 reduce/reduce gcc -o p/parse.o -c -g -DIN_GCC -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -fno-common -DHAVE_CONFIG_H -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -fno-common -pedantic -Wno-long-long -I. -Ip -I../../gcc-3.4-20040702/gcc -I../../gcc-3.4-20040702/gcc/p -I../../gcc-3.4-20040702/gcc/../include -DGPC -DGPC_UNITS_DIR="/opt/gcc-3.4/lib/gcc/i686-pc-linux-gnu/3.4.1/units" -I../../gcc-3.4-20040702/gcc/p ../../gcc-3.4-20040702/gcc/p/parse.c parse.c:380: warning: useless keyword or type name in empty declaration parse.c:380: warning: empty declaration parse.c: In function `yydoAction': parse.c:8160: error: `USE_ASSERT_RATHER_THAN_ABORT' undeclared (first use in this function) parse.c:8160: error: (Each undeclared identifier is reported only once parse.c:8160: error: for each function it appears in.) parse.c: In function `yyglrReduce': parse.c:8276: error: `USE_ASSERT_RATHER_THAN_ABORT' undeclared (first use in this function) parse.c: In function `yysplitStack': parse.c:8314: error: `USE_ASSERT_RATHER_THAN_ABORT' undeclared (first use in this function) parse.c: In function `yyresolveStates': parse.c:8413: error: `USE_ASSERT_RATHER_THAN_ABORT' undeclared (first use in this function) parse.c: In function `yyresolveAction': parse.c:8444: error: `USE_ASSERT_RATHER_THAN_ABORT' undeclared (first use in this function) parse.c: In function `yyprocessOneStack': parse.c:8637: error: `USE_ASSERT_RATHER_THAN_ABORT' undeclared (first use in this function) parse.y: At top level: parse.y:2837: warning: `locations' defined but not used make[2]: *** [p/parse.o] Error 1 make[2]: Leaving directory `/home/dave2/gcc/gcc-3.4/gcc' make[1]: *** [stage1_build] Error 2 make[1]: Leaving directory `/home/dave2/gcc/gcc-3.4/gcc' make: *** [bootstrap] Error 2
I use Gentoo 2004.1 default bison :
bison -V bison (GNU Bison) 1.875
Thanks, David
David Kredba wrote:
Hello.
I ran into another problem.
gcc -g -DIN_GCC -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -pedantic -Wno-long-long -fno-common -DHAVE_CONFIG_H -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -pedantic -Wno-long-long -fno-common -pedantic -Wno-long-long -o xgpc p/gpc.o prefix.o version.o \ intl.o ../libiberty/libiberty.a gcc -o p/diagnostic.o -c -g -DIN_GCC -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -fno-common -DHAVE_CONFIG_H -I. -Ip -I../../gcc-3.4-20040702/gcc -I../../gcc-3.4-20040702/gcc/p -I../../gcc-3.4-20040702/gcc/../include -DGPC ../../gcc-3.4-20040702/gcc/diagnostic.c echo "expect 16 shift/reduce and 30 reduce/reduce conflicts" >&2 expect 16 shift/reduce and 30 reduce/reduce conflicts cd ../../gcc-3.4-20040702/gcc/p && bison -o parse.c parse.y parse.y: conflicts: 16 shift/reduce, 295 reduce/reduce gcc -o p/parse.o -c -g -DIN_GCC -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -fno-common -DHAVE_CONFIG_H -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -fno-common -pedantic -Wno-long-long -I. -Ip -I../../gcc-3.4-20040702/gcc -I../../gcc-3.4-20040702/gcc/p -I../../gcc-3.4-20040702/gcc/../include -DGPC -DGPC_UNITS_DIR="/opt/gcc-3.4/lib/gcc/i686-pc-linux-gnu/3.4.1/units" -I../../gcc-3.4-20040702/gcc/p ../../gcc-3.4-20040702/gcc/p/parse.c parse.c:380: warning: useless keyword or type name in empty declaration parse.c:380: warning: empty declaration parse.c: In function `yydoAction': parse.c:8160: error: `USE_ASSERT_RATHER_THAN_ABORT' undeclared (first
<snip>
I use Gentoo 2004.1 default bison :
bison -V bison (GNU Bison) 1.875
gpc needs bison 1.875c. I have added pregenerated parser files to the Web page for people with older bison.
Earler David Kredba wrote: <snip>
../../gcc-3.4-20040702/gcc/p/mk_lang_opt < ../../gcc-3.4-20040702/gcc/p/opts.sum > "../../gcc-3.4-20040702/gcc/p/lang.opt" /bin/sh: line 1: ../../gcc-3.4-20040702/gcc/p/mk_lang_opt: P??stup odm?tnut make[2]: *** [../../gcc-3.4-20040702/gcc/p/lang.opt] Error 126 make[2]: Leaving directory `/home/dave2/gcc/gcc-3.4/gcc' make[1]: *** [stage1_build] Error 2 make[1]: Leaving directory `/home/dave2/gcc/gcc-3.4/gcc' make: *** [bootstrap] Error 2
There is lang.opt file with 0 Byte size in gcc-3.4-20040702/gcc/p folder.
Mk_lang_opt has no executable flag. I ran tar xzf to unpack gpc archive an diffs to gpc and gcc.
If I set executable flag to mk_lang_opt file, build process continues.
I had never unpack gpc tarball with p option, like tar xzpf gpc-20040516.tar.gz and build process always works fine.
I can see that mk_lang_opt comes from update27h.diff, so tar xzpf to gpc tarball is not needed. ../../gcc-3.4-20040702/gcc/p/mk_lang_opt < ../../gcc-3.4-20040702/gcc/p/opts.sum > "../../gcc-3.4-20040702/gcc/p/lang.opt" /bin/sh: line 1: ../../gcc-3.4-20040702/gcc/p/mk_lang_opt: P??stup odm?tnut make[2]: *** [../../gcc-3.4-20040702/gcc/p/lang.opt] Error 126 make[2]: Leaving directory `/home/dave2/gcc/gcc-3.4/gcc' make[1]: *** [stage1_build] Error 2 make[1]: Leaving directory `/home/dave2/gcc/gcc-3.4/gcc' make: *** [bootstrap] Error 2
There is lang.opt file with 0 Byte size in gcc-3.4-20040702/gcc/p folder.
Existing file was truncated by redirection.
Mk_lang_opt has no executable flag. I ran tar xzf to unpack gpc archive an diffs to gpc and gcc.
If I set executable flag to mk_lang_opt file, build process continues.
I had never unpack gpc tarball with p option, like tar xzpf gpc-20040516.tar.gz and build process always works fine.
I can see that mk_lang_opt comes from update27h.diff, so tar xzpf to gpc tarball is not needed.
I don`t now if patch can set executable flag to mk_lang_opt file but I think that not.
Is executable flag really on mk_lang_opt file needed to bootstrap compiler or I am doing some error ?
The patch contains up to date 'lang.opt'. I suspect that some timestamp weirdness is causing rebuild. Hmm, smells like nanosecond timestamps -- probably patch creates 'mk_lang_opt' few microseconds later then 'lang.opt'. The executable flag is needed when source is changed.
I`ll do upgrade to newer bison.
Thanks very much.
I found this :
2004-07-08 23:01:33.297671408 +0200 lang.opt 2004-07-08 23:01:33.407366288 +0200 mk_lang_opt
Regards,
David