[Top][All Lists]

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

Re: (IMPORTANT/URGENT) Regarding Missing Files in bash source code?

From: Greg Wooledge
Subject: Re: (IMPORTANT/URGENT) Regarding Missing Files in bash source code?
Date: Fri, 17 Jul 2020 10:20:31 -0400
User-agent: Mutt/1.10.1 (2018-07-13)

On Fri, Jul 17, 2020 at 10:10:21PM +0800, Humanities Clinic wrote:
> When I run make (I run it with the -i option), I see the following
> output for the first invoked command:
> bison -y -d ./parse.y
> ./parse.y: warning: 1 shift/reduce conflict [-Wconflicts-sr]
> bison: /usr/local/Cellar/bison/3.3.2/share/bison/m4sugar/m4sugar.m4: cannot
> open: No such file or directory

This sounds like bison is not correctly installed on your system.
If it were *my* system, I would reinstall bison from its source
code.  Either that, or figure out why that particular file isn't
being found.  Reinstalling is probably easier.

> make: [y.tab.c] Error 1 (ignored)
> May I know what does the last line mean? I understand from
> https://www.gnu.org/software/make/manual/html_node/Error-Messages.html that
> it means that invoking y.tab.c returned an error code of 1. The thing is,
> there's no command that involves the file y.tab.c? I don't really
> understand how y.tab.c came into the picture.

y.tab.c is the name of the file that make is trying to create.

When building bash from a released tarball, you do not need bison.
Chet already ran bison on the parser source files to produce bison's
output, and included that in the release tarball, in order to reduce
the number of build dependencies.

But, if you are *not* using a release tarball, or if you modified
one of the parser source files, then bison has to be run during the
build.  (This may sometimes happen when patching, for example.)

reply via email to

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