[Top][All Lists]

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

Re: Build failure: can't read libinterp/corefcn/ No

From: Mike Miller
Subject: Re: Build failure: can't read libinterp/corefcn/ No such file or directory
Date: Wed, 30 Jan 2019 10:40:09 -0800
User-agent: Mutt/1.10.1 (2018-07-13)

On Tue, Jan 29, 2019 at 18:08:40 -0500, Andrew Janke wrote:
> I'm getting build failures when attempting to build either stable or
> default. Builds using these same build scripts used to work; I don't know
> what's changed.

My guess is that your build environment has updated bison recently.
Bison 3.3.0 and 3.3.1 were both released in the last week.

> Here's the error from make:
> /usr/local/opt/gnu-sed/bin/gsed: can't read
> libinterp/corefcn/ No such file or directory
> make: *** [libinterp/corefcn/oct-tex-parser.h] Error 2

Yeah, this file is supposed to be created by bison.

> configure is complaining about not finding bison, even though I have it
> installed (GNU bison 3.3.1) and on the $PATH:

You missed the first warning block, which is a little more interesting:

    configure: WARNING:
    I wasn't able to find a suitable style for declaring the api prefix
    in a bison input file so I'm disabling bison.  We expect bison to
    understand the '%define api.prefix { PREFIX }' syntax.

Octave's configure is attempting to do a feature test on bison, and it
failed. Unfortunately it looks like we don't have a good diagnostic for
why it failed. But it looks like configure is not happy with bison 3.3
right now. Can you take this to the bug tracker?



Attachment: signature.asc
Description: PGP signature

reply via email to

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