------- Comment #2 from wilson at gcc dot gnu dot org 2008-01-08 23:20 -------
GCC is assuming use of GNU bison instead of yacc here. Install GNU bison,
reconfigure, and the problem will go away.
GCC release tar balls have pre-generated output files with appropriate file
time stamps, so that end users do not need bison or other tools in order to do
a build. If you use one of these unchanged, then you should not have this
problem. However, if you extract a release, and then do anything that changes
file timestamps (make a copy, check it into a Source Code Management
repository, etc), then you will need bison and other tools in order to do a
build. If you check out a release from the GNU GCC repository, then the same
rules apply. If you use a snapshot from the GNU GCC ftp site, then the same
rules apply. Etc.
Alternatively, you can always do something like "touch intl/plural.c" to fix
the timestamps, and prevent make from trying to rebuild the file. You might
have to do this for multiple files. The command "contrib/gcc_update --touch"
should do this for you, but I haven't tried it.
Information about tools needed to work on gcc can be found here:
http://gcc.gnu.org/install/prerequisites.html
Bison is mentioned as necessary for *.y files.
gcc-3.4 is no longer maintained from GNU GCC developers, so if there is a bug
here, we aren't going to fix it, unless it also exists in a current GCC
release.
--
wilson at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |wilson at gcc dot gnu dot
| |org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34259
