Build failure: can't read libinterp/corefcn/oct-tex-parser.cc-t: No such file or directory

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Build failure: can't read libinterp/corefcn/oct-tex-parser.cc-t: No such file or directory

apjanke-floss
Hi, Octave folks,

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.

Here's the error from make:

rm -f libinterp/corefcn/oct-tex-parser.cc-t
libinterp/corefcn/oct-tex-parser.cc-tt && \
     /bin/sh ./build-aux/ylwrap libinterp/corefcn/oct-tex-parser.yy
y.tab.c libinterp/corefcn/oct-tex-parser.cc-t y.tab.h
libinterp/corefcn/oct-tex-parser.h y.output
libinterp/corefcn/oct-tex-parser.output -- ./build-aux/missing bison
-dv  && \
     /usr/local/opt/gnu-sed/bin/gsed
's|"libinterp/corefcn/oct-tex-parser\.cc-t"|"libinterp/corefcn/oct-tex-parser.cc"|g'
libinterp/corefcn/oct-tex-parser.cc-t >
libinterp/corefcn/oct-tex-parser.cc-tt && \
     mv libinterp/corefcn/oct-tex-parser.cc-tt
libinterp/corefcn/oct-tex-parser.cc-t && \
       if [ -s libinterp/corefcn/oct-tex-parser.cc-t ]; then /bin/sh
./build-aux/move-if-change libinterp/corefcn/oct-tex-parser.cc-t
libinterp/corefcn/oct-tex-parser.cc; else echo
"libinterp/corefcn/oct-tex-parser.cc-t is empty!" 1>&2; rm -f
libinterp/corefcn/oct-tex-parser.cc-t; exit 1; fi
updating oct-tex-parser.output
updating oct-tex-parser.tab.cc
updating oct-tex-parser.tab.hh
/usr/local/opt/gnu-sed/bin/gsed: can't read
libinterp/corefcn/oct-tex-parser.cc-t: No such file or directory
make: *** [libinterp/corefcn/oct-tex-parser.h] Error 2

Happens whether I'm running multiple jobs with "make -j 8" or a single job.

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


configure: WARNING:

I didn't find bison, or the version of bison that I found does not
support all the features that are required, but it's only a problem
if you need to reconstruct parse.cc, which is the case if you're
building from VCS sources.

$ bison --version
bison (GNU Bison) 3.3.1
Written by Robert Corbett and Richard Stallman.

Copyright (C) 2019 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
$ which bison
/usr/local/opt/bison/bin/bison


Full build logs: https://gist.github.com/015e1243f54d300461f66008f8609e1a

Anybody know what's going on here and how to fix it?


Cheers,
Andrew


Reply | Threaded
Open this post in threaded view
|

Re: Build failure: can't read libinterp/corefcn/oct-tex-parser.cc-t: No such file or directory

Mike Miller-4
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/oct-tex-parser.cc-t: 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,

--
mike



signature.asc (849 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Build failure: can't read libinterp/corefcn/oct-tex-parser.cc-t: No such file or directory

apjanke-floss


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/oct-tex-parser.cc-t: 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: https://savannah.gnu.org/bugs/index.php?55613

Cheers,
Andrew




signature.asc (849 bytes) Download Attachment