public inbox for
 help / color / mirror / Atom feed
From: "Pierre Muller" <>
To: "'John Long'" <>
Cc: <>
Subject: RE: Build problem on OpenBSD MIPS
Date: Thu, 04 Jul 2013 15:22:00 -0000	[thread overview]
Message-ID: <000001ce78ca$4da37d10$e8ea7730$> (raw)
In-Reply-To: <>

  Maybe it is a problem with the tool that is used
to generate  the c-exp.c from the c-exp.y source.

I have the impression that OpenBSD often tends to still use old GNU tools...

  On my successful build,
c_print_token is used in YYPRINT macro:

$ grep YYPRINT c-*.c -n -A 5
398:#define YYPRINT(FILE, TYPE, VALUE) c_print_token (FILE, TYPE, VALUE)
400-/* Line 390 of yacc.c  */
401-#line 402 "c-exp.c"
403-#ifdef short
867:# ifdef YYPRINT
868-/* YYTOKNUM[YYLEX-NUM] -- Internal token number corresponding to
869-   token YYLEX-NUM.  */
870-static const yytype_uint16 yytoknum[] =
872-       0,   256,   257,   258,   259,   260,   261,   262,   263,   264,
1589:# ifdef YYPRINT
1590-  if (yytype < YYNTOKENS)
1591:    YYPRINT (yyoutput, yytoknum[yytype], *yyvaluep);
1592-# else
1593-  YYUSE (yyoutput);
1594-# endif
1595-  switch (yytype)
1596-    {
5989:/* This is called via the YYPRINT macro when parser debugging is
5990-   enabled.  It prints a token's value.  */
5992-static void
5993-c_print_token (FILE *file, int type, YYSTYPE value)

$ head c-exp.c
/* A Bison parser, made by GNU Bison 2.7.  */

/* Bison implementation for Yacc-like parsers in C

Could you check if YYPRINT is used in your c-exp.c file,
and which tool was used to create it (it will probably be mentioned 
in the header like here).

Pierre Muller

  reply	other threads:[~2013-07-04 15:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-04 15:00 John Long
2013-07-04 15:22 ` Pierre Muller [this message]
2013-07-04 15:39   ` John Long
2013-07-04 16:28     ` Pierre Muller
2013-07-04 17:28       ` John Long

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:

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

  git send-email \
    --in-reply-to='000001ce78ca$4da37d10$e8ea7730$' \ \ \ \

* 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).