[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: Andrew Janke
Subject: Re: Build failure: can't read libinterp/corefcn/ No such file or directory
Date: Thu, 31 Jan 2019 03:07:11 -0500
User-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:60.0) Gecko/20100101 Thunderbird/60.4.0

On 1/30/19 1:40 PM, Mike Miller wrote:
> 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?
> Thanks,

Good call. I had upgraded from Bison 3.2.4 to 3.3.1. Downgrading to
3.2.4 fixed it.

Bug report:


Attachment: signature.asc
Description: OpenPGP digital signature

reply via email to

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