octave-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #55613] Build failure with bison 3.3.1


From: Mike Miller
Subject: [Octave-bug-tracker] [bug #55613] Build failure with bison 3.3.1
Date: Thu, 31 Jan 2019 14:25:29 -0500 (EST)
User-agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.98 Safari/537.36

Update of bug #55613 (project octave):

                  Status:               Need Info => Confirmed              

    _______________________________________________________

Follow-up Comment #2:

Here is the new behavior from bison 3.3.1:


$ cat conftest.yy
%define api.prefix {foo_}
%start input
%%
input:;
%%
$ bison -y conftest.yy 
conftest.yy:1.1-7: warning: POSIX Yacc does not support %define [-Wyacc]
 %define api.prefix {foo_}
 ^~~~~~~


The '-y' option is added automatically by autoconf's support for bison/yacc to
make bison behave like POSIX yacc. The warning is only emitted when the '-y'
option is present, and only with bison version 3.3 or later.

Octave's configure script captures both stdout and stderr and expects them to
be empty to test for success. This warning is interpreted as a failure and so
configure thinks that bison doesn't work with any of the known formats.

In the meantime, autoconf has been changed to drop the '-y' option on bison
(https://git.savannah.gnu.org/cgit/autoconf.git/commit/?id=42761668c0300afa7f8bf5ba736458a818cd5d15),
but that version of autoconf has not been released yet.

    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?55613>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]