This is the mail archive of the
insight@sourceware.org
mailing list for the Insight project.
RE: Build problem on OpenBSD MIPS
- From: "Pierre Muller" <pierre dot muller at ics-cnrs dot unistra dot fr>
- To: "'John Long'" <codeblue at inbox dot lv>
- Cc: <insight at sourceware dot org>
- Date: Thu, 4 Jul 2013 17:22:30 +0200
- Subject: RE: Build problem on OpenBSD MIPS
- References: <20130704145949 dot GA9402 at inbox dot lv>
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)
399-
400-/* Line 390 of yacc.c */
401-#line 402 "c-exp.c"
402-
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[] =
871-{
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. */
5991-
5992-static void
5993-c_print_token (FILE *file, int type, YYSTYPE value)
5994-{
$ 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