From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21584 invoked by alias); 4 Jul 2013 15:22:45 -0000 Mailing-List: contact insight-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: insight-owner@sourceware.org Received: (qmail 21563 invoked by uid 89); 4 Jul 2013 15:22:42 -0000 X-Spam-SWARE-Status: No, score=-1.7 required=5.0 tests=AWL,BAYES_00,KHOP_THREADED,MSGID_MULTIPLE_AT,TW_YY autolearn=no version=3.3.1 Received: from mailhost.u-strasbg.fr (HELO mailhost.u-strasbg.fr) (130.79.201.42) by sourceware.org (qpsmtpd/0.84/v0.84-167-ge50287c) with ESMTP; Thu, 04 Jul 2013 15:22:40 +0000 Received: from md16.u-strasbg.fr (md16.u-strasbg.fr [130.79.200.206]) by mailhost.u-strasbg.fr (8.14.3/jtpda-5.5pre1) with ESMTP id r64FMXi1013887 ; Thu, 4 Jul 2013 17:22:33 +0200 (CEST) (envelope-from pierre.muller@ics-cnrs.unistra.fr) Received: from ms17.u-strasbg.fr (ms17.u-strasbg.fr [130.79.204.117]) by md16.u-strasbg.fr (8.14.3/jtpda-5.5pre1) with ESMTP id r64FMXQH004949 ; Thu, 4 Jul 2013 17:22:33 +0200 (envelope-from pierre.muller@ics-cnrs.unistra.fr) Received: from E6510Muller (gw-ics.u-strasbg.fr [130.79.210.225]) (Authenticated sender: mullerp) by ms17.u-strasbg.fr (Postfix) with ESMTPSA id 3D4231FD9D; Thu, 4 Jul 2013 17:22:32 +0200 (CEST) From: "Pierre Muller" To: "'John Long'" Cc: References: <20130704145949.GA9402@inbox.lv> In-Reply-To: <20130704145949.GA9402@inbox.lv> Subject: RE: Build problem on OpenBSD MIPS Date: Thu, 04 Jul 2013 15:22:00 -0000 Message-ID: <000001ce78ca$4da37d10$e8ea7730$@muller@ics-cnrs.unistra.fr> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-SW-Source: 2013-q3/txt/msg00007.txt.bz2 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