Re: Bison autoconf tests

[Rik-4]

On 03/02/2013 06:33 AM, [hidden email] wrote:

Message: 3
Date: Sat, 2 Mar 2013 14:50:06 +0100
From: Sander van Rijn [hidden email]
To: marco atzeri [hidden email]
Cc: [hidden email]
Subject: Re: Toward a reentrant/thread safe parser and lexer
Message-ID:
	[hidden email]
Content-Type: text/plain; charset="iso-8859-1"

On 2 March 2013 05:50, marco atzeri [hidden email] wrote:

>
> Hi John,
>
> changeset:   16167:22bb3aa9f025
> user:        John W. Eaton [hidden email]
> date:        Fri Mar 01 07:18:18 2013 -0500
> summary:     make push parser interface partially work
>
> breaks build on cygwin:
>
> make[2]: Entering directory `/pub/hg/octave_build/**libinterp'
> /usr/bin/sed < ../../octave/libinterp/interp-**core/mxarray.in.h \
>   -e "s|%NO_EDIT_WARNING%|DO NOT EDIT!  Generated automatically from
> mxarray.in.h by Make.|" \
>   -e "s|%OCTAVE_IDX_TYPE%|int|" > interp-core/mxarray.h-t
> mv interp-core/mxarray.h-t interp-core/mxarray.h
> if test -n "perl"; then \
>   ../../octave/libinterp/mk-**errno-list --perl "perl" <
> ../../octave/libinterp/interp-**core/oct-errno.in.cc >
> interp-core/oct-errno.cc-t; \
> elif test -n "python"; then \
>   ../../octave/libinterp/mk-**errno-list --python "python" <
> ../../octave/libinterp/interp-**core/oct-errno.in.cc >
> interp-core/oct-errno.cc-t; \
> else \
>   /usr/bin/sed '/@SYSDEP_ERRNO_LIST@/D' ../../octave/libinterp/interp-**
> core/oct-errno.in.cc > interp-core/oct-errno.cc-t; \
> fi
> mv interp-core/oct-errno.cc-t interp-core/oct-errno.cc
> making interpfcn/defaults.h from ../../octave/libinterp/**
> interpfcn/defaults.in.h
> gawk -v emit_graphics_props=1 -f ../../octave/libinterp/**genprops.awk
> ../../octave/libinterp/**interpfcn/graphics.in.h >
> interpfcn/graphics-props.cc-t
> mv interpfcn/graphics-props.cc-t interpfcn/graphics-props.cc
> gawk -f ../../octave/libinterp/**genprops.awk ../../octave/libinterp/**interpfcn/graphics.in.h

> > interpfcn/graphics.h-t

> mv interpfcn/graphics.h-t interpfcn/graphics.h
> /bin/sh ../../octave/build-aux/ylwrap ../../octave/libinterp/parse-**tree/lex.ll
> lex.octave_.c parse-tree/lex.cc -- flex -I -I
> /bin/sh ../../octave/build-aux/ylwrap ../../octave/libinterp/parse-**tree/oct-parse.yy
> y.tab.c parse-tree/oct-parse.cc y.tab.h parse-tree/oct-parse.h y.output
> parse-tree/oct-parse.output -- bison -y -dv
> /pub/hg/octave_build/**libinterp/../../octave/**libinterp/parse-tree/oct-*
> *parse.yy:169.17: invalid character: `-'
> /pub/hg/octave_build/**libinterp/../../octave/**libinterp/parse-tree/oct-*
> *parse.yy:169.18-21: syntax error, unexpected identifier
> Makefile:8977: recipe for target `parse-tree/oct-parse.cc' failed
> make[2]: *** [parse-tree/oct-parse.cc] Error 1
>
> MArco
>
>

I had the same problem yesterday, was caused by Bison version 2.4. Problem
was solved for me by manually updating to 2.7 (or any version later than
2.4)

3/2/13

Marco,

I have the same problem.   The issue is that Bison changed format for one of their options between 2.4 and 2.5.  The feature desired, push-pull parser, didn't even exist before 2.4.  An autoconf test will hopefully be written soon to deal with these three different cases. 

--Rik

[John W. Eaton]

On 03/02/2013 10:07 AM, Rik wrote:

> I have the same problem. The issue is that Bison changed format for one
> of their options between 2.4 and 2.5. The feature desired, push-pull
> parser, didn't even exist before 2.4. An autoconf test will hopefully be
> written soon to deal with these three different cases.

I'm working on it now.

jwe

[John W. Eaton]

On 03/02/2013 10:46 AM, John W. Eaton wrote:
> On 03/02/2013 10:07 AM, Rik wrote:
>
>> I have the same problem. The issue is that Bison changed format for one
>> of their options between 2.4 and 2.5. The feature desired, push-pull
>> parser, didn't even exist before 2.4. An autoconf test will hopefully be
>> written soon to deal with these three different cases.
>
> I'm working on it now.

I checked in a changeset:

   http://hg.savannah.gnu.org/hgweb/octave/rev/39096b290a2f

jwe

[nrolland]

I think this way of determining the idiom relies on the system bison and not the bison any dependency  provided as an argument to configure.sh

Installing from brew asks provide bison as a -L library.
My system has bison 2.3 by default, and this script disable bison entirely as it fails to recognize the idiom based on a version which does not contain it.