public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "philippe dot vereecke at siih5962 dot fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/34259] Compile gcc 3.4.6 on tru64 unix v5.1b problem with yacc syntax
Date: Wed, 28 Nov 2007 09:33:00 -0000	[thread overview]
Message-ID: <20071128093252.29509.qmail@sourceware.org> (raw)
In-Reply-To: <bug-34259-15448@http.gcc.gnu.org/bugzilla/>



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


  reply	other threads:[~2007-11-28  9:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-28  9:31 [Bug bootstrap/34259] New: " philippe dot vereecke at siih5962 dot fr
2007-11-28  9:33 ` philippe dot vereecke at siih5962 dot fr [this message]
2008-01-09  0:14 ` [Bug bootstrap/34259] " wilson at gcc dot gnu dot org
     [not found] <bug-34259-4@http.gcc.gnu.org/bugzilla/>
2012-01-19  5:43 ` pinskia at gcc dot gnu.org
2012-01-19  5:46 ` P-VEREECKE at siih5962 dot fr

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20071128093252.29509.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).