when bison is not installed, configure reports only a warning, instead of an error. Consequently, the following make-command fails.
automake 1.9 autoconf 2.59a
Are you building from the source tarball or from CVS? If from the source tarball, you don't need bison which is why it is just a warning. Otherwise this is a bug in the release process if bison is now required (and a regression). What is the current error you are getting building GCC?
Subject: Re: configure reports only a warning when bison is not installed "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> writes: | Are you building from the source tarball or from CVS? | If from the source tarball, you don't need bison which is why it is just a warning. | Otherwise this is a bug in the release process if bison is now required (and a regression). | What is the current error you are getting building GCC? The problem as I was able to reproduce on Peter's machine yesterday is the following: gcc-core from release repository does not seem to contain w pregenerated c-parse.c. At build time, the build machiery attempts to generate it from c-parse.in and was looking for bison which Peter did not have. For some reasons the build did not stop for clear and unambiguous reason, (and even sooner aat configure time). If we now require bison for gcc-core, then we should check that at configure time and abort. -- Gaby
Ok, we don't require bison at least before, sounds like the release package is messed up.
Subject: Re: [4.0/4.1 Regression] build now requires bision "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> writes: | What |Removed |Added | ---------------------------------------------------------------------------- | CC|gdr at cs dot tamu dot edu |gdr at gcc dot gnu dot org Thanks! :-) -- Gaby
CCing the release manager.
I don't understand this PR. Here is evidence that c-parse.c is in fact included: $ tar tjf gcc-core-4.0.1-20050616.tar.bz2 | grep c-parse gcc-4.0.1-20050616/gcc/c-parse.in gcc-4.0.1-20050616/gcc/c-parse.y gcc-4.0.1-20050616/gcc/c-parse.c Andrew, are you sure that c-parse.c is not present?
There's nothing that suggests that we can reproduce this bug, so I've closed it.