From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31480 invoked by alias); 4 Jul 2013 16:28:23 -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 31471 invoked by uid 89); 4 Jul 2013 16:28:22 -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 16:27:55 +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 r64GRmh8026256 ; Thu, 4 Jul 2013 18:27:48 +0200 (CEST) (envelope-from pierre.muller@ics-cnrs.unistra.fr) Received: from ms15.u-strasbg.fr (ms15.u-strasbg.fr [130.79.204.115]) by md16.u-strasbg.fr (8.14.3/jtpda-5.5pre1) with ESMTP id r64GRmp6018486 ; Thu, 4 Jul 2013 18:27:48 +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 ms15.u-strasbg.fr (Postfix) with ESMTPSA id C7B851FD88; Thu, 4 Jul 2013 18:27:46 +0200 (CEST) From: "Pierre Muller" To: "'John Long'" Cc: References: <20130704145949.GA9402@inbox.lv> <000001ce78ca$4da37d10$e8ea7730$@muller@ics-cnrs.unistra.fr> <20130704153924.GB9402@inbox.lv> In-Reply-To: <20130704153924.GB9402@inbox.lv> Subject: RE: Build problem on OpenBSD MIPS Date: Thu, 04 Jul 2013 16:28:00 -0000 Message-ID: <000301ce78d3$6adbdef0$40939cd0$@muller@ics-cnrs.unistra.fr> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-SW-Source: 2013-q3/txt/msg00009.txt.bz2 Hi John, it indeed seems to be that your build doesn't use YACC debugging and that this could be the reason of the unused function that generates the error. You could: 1) delete c-exp.c in the build directory and check how this file is regenerated by the make script. a simple=20 rm c-exp.y make c-exp.y should be enough for this. 2) Test recompiling the new c-exp.c file make c-exp.o should be enough. If you do get again the same error, you can=20 bypass it simply by disabling the "consider a warning as an error" option which is the -Werror option of GNU C compiler. 3) To do this, simply run make c-exp.o WERROR_CFLAGS=3D"" 4) After that, a normal=20 make gdb insight should work. If point 2) still fails, it would be worthwhile to state that problem to gdb@sourceware.org specifying how c-exp.c was regenerated at point 1 (and the version of the executable used, which might well be of importance here). Hopefully you will be able to complete insight compilation... Pierre Muller > -----Message d'origine----- > De=A0: insight-owner@sourceware.org [mailto:insight-owner@sourceware.org]= De > la part de John Long > Envoy=E9=A0: jeudi 4 juillet 2013 17:39 > =C0=A0: Pierre Muller > Cc=A0: insight@sourceware.org > Objet=A0: Re: Build problem on OpenBSD MIPS >=20 > On Thu, Jul 04, 2013 at 05:22:30PM +0200, Pierre Muller wrote: > > 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[] =3D > > 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 > > >=20 > Hi, I have no idea what I am doing so I just tried your commands as is. Here > is the output: >=20 > grep YYPRINT c-*.c -n -A 5 > 146:#define YYPRINT(FILE, TYPE, VALUE) c_print_token (FILE, TYPE, VALUE) > 147-#line 148 "c-exp.c" > 148-#define INT 257 > 149-#define FLOAT 258 > 150-#define DECFLOAT 259 > 151-#define STRING 260 > 4233:/* This is called via the YYPRINT macro when parser debugging is > 4234- enabled. It prints a token's value. */ > 4235- > 4236-static void > 4237-c_print_token (FILE *file, int type, YYSTYPE value) > 4238-{ > user:/tmp/insight-cvs/insight/gdb$ >=20 > head c-exp.c > #include > #include > #define YYBYACC 1 > #define YYMAJOR 1 > #define YYMINOR 9 > #define YYLEX yylex() > #define YYEMPTY -1 > #define yyclearin (yychar=3D(YYEMPTY)) > #define yyerrok (yyerrflag=3D0) > #define YYRECOVERING() (yyerrflag!=3D0) > user:/tmp/insight-cvs/insight/gdb$ >=20 > I don't see that YYPRINT is used anywhere else in c-exp.c >=20 > Does the following suggest this isn't going to be used in a normal build? >=20 > /* This is called via the YYPRINT macro when parser debugging is > enabled. It prints a token's value. */ >=20 > static void > c_print_token (FILE *file, int type, YYSTYPE value) > { > switch (type) > { > case INT: > fprintf (file, "typed_val_int<%s, %s>", > TYPE_SAFE_NAME (value.typed_val_int.type), >=20 > Thanks, >=20 > /jl