[Bug bootstrap/34259] Compile gcc 3.4.6 on tru64 unix v5.1b problem with yacc syntax

[Bug bootstrap/34259] Compile gcc 3.4.6 on tru64 unix v5.1b problem with yacc syntax

[pinskia at gcc dot gnu.org]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34259

Andrew Pinski <pinskia at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|                            |INVALID

--- Comment #3 from Andrew Pinski <pinskia at gcc dot gnu.org> 2012-01-19 05:31:52 UTC ---
Invalid based on Jim's comments.

[Bug bootstrap/34259] Compile gcc 3.4.6 on tru64 unix v5.1b problem with yacc syntax

[P-VEREECKE at siih5962 dot fr]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34259

--- Comment #4 from P-VEREECKE at siih5962 dot fr 2012-01-19 05:32:49 UTC ---
Je suis absent du 16/1/2012 au 18/1/2012 inclus.

Je traiterai votre message à mon retour le 19/1/2012.

Pour toute urgence, contacter la cellule d'appels au 44481.

Merci.

[Bug bootstrap/34259] Compile gcc 3.4.6 on tru64 unix v5.1b problem with yacc syntax

[wilson at gcc dot gnu dot org]

------- 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

[Bug bootstrap/34259] Compile gcc 3.4.6 on tru64 unix v5.1b problem with yacc syntax

[philippe dot vereecke at siih5962 dot fr]

------- Comment #1 from philippe dot vereecke at siih5962 dot fr  2007-11-28 09:32 -------
yacc --name-prefix=__gettext --output plural.c
/usr/local/gcc/src/gcc-3.4.6/intl
/plural.y
usage: yacc -svdlt [-b prefix] [-p sym_prefix] [-P path] [-N num] file
*** Exit 1
Stop.
*** Exit 1
Stop.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34259