Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > gnu.bash.bug > #16573

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

Path csiph.com!goblin1!goblin.stu.neva.ru!usenet.stanford.edu!not-for-mail
From Greg Wooledge <wooledg@eeg.ccf.org>
Newsgroups gnu.bash.bug
Subject Re: (IMPORTANT/URGENT) Regarding Missing Files in bash source code?
Date Fri, 17 Jul 2020 10:20:31 -0400
Lines 34
Approved bug-bash@gnu.org
Message-ID <mailman.381.1594995664.2306.bug-bash@gnu.org> (permalink)
References <CAFoojOo6BXD77zTSMr+jRS5=FoxiuDZ57u4F-FqK3vVcMZmvJA@mail.gmail.com> <20200624120450.GA22833@eeg.ccf.org> <CAFoojOpSsak8H4K6nFL1z19WV5mRy9HTB5ujVNep=XKV5YoW_A@mail.gmail.com> <20200717142031.GA22833@eeg.ccf.org>
NNTP-Posting-Host lists.gnu.org
Mime-Version 1.0
Content-Type text/plain; charset=us-ascii
X-Trace usenet.stanford.edu 1594995664 1525 209.51.188.17 (17 Jul 2020 14:21:04 GMT)
X-Complaints-To action@cs.stanford.edu
Cc bash-maintainers@gnu.org, bug-bash@gnu.org, help-bash@gnu.org
To Humanities Clinic <humanitiesclinic@gmail.com>
Envelope-to bug-bash@gnu.org
Mail-Followup-To Humanities Clinic <humanitiesclinic@gmail.com>, bash-maintainers@gnu.org, bug-bash@gnu.org, help-bash@gnu.org
Content-Disposition inline
In-Reply-To <CAFoojOpSsak8H4K6nFL1z19WV5mRy9HTB5ujVNep=XKV5YoW_A@mail.gmail.com>
User-Agent Mutt/1.10.1 (2018-07-13)
Received-SPF none client-ip=139.137.100.1; envelope-from=wooledg@eeg.ccf.org; helo=mail.eeg.ccf.org
X-detected-operating-system by eggs.gnu.org: First seen = 2020/07/17 10:20:32
X-ACL-Warn Detected OS = Linux 2.2.x-3.x [generic] [fuzzy]
X-Spam_score_int -8
X-Spam_score -0.9
X-Spam_bar /
X-Spam_report (-0.9 / 5.0 requ) BAYES_00=-1.9, KHOP_HELO_FCRDNS=1, SPF_HELO_NONE=0.001, SPF_NONE=0.001 autolearn=no autolearn_force=no
X-Spam_action no action
X-BeenThere bug-bash@gnu.org
X-Mailman-Version 2.1.23
Precedence list
List-Id Bug reports for the GNU Bourne Again SHell <bug-bash.gnu.org>
List-Unsubscribe <https://lists.gnu.org/mailman/options/bug-bash>, <mailto:bug-bash-request@gnu.org?subject=unsubscribe>
List-Archive <https://lists.gnu.org/archive/html/bug-bash>
List-Post <mailto:bug-bash@gnu.org>
List-Help <mailto:bug-bash-request@gnu.org?subject=help>
List-Subscribe <https://lists.gnu.org/mailman/listinfo/bug-bash>, <mailto:bug-bash-request@gnu.org?subject=subscribe>
X-Mailman-Original-Message-ID <20200717142031.GA22833@eeg.ccf.org>
X-Mailman-Original-References <CAFoojOo6BXD77zTSMr+jRS5=FoxiuDZ57u4F-FqK3vVcMZmvJA@mail.gmail.com> <20200624120450.GA22833@eeg.ccf.org> <CAFoojOpSsak8H4K6nFL1z19WV5mRy9HTB5ujVNep=XKV5YoW_A@mail.gmail.com>
Xref csiph.com gnu.bash.bug:16573

Show key headers only | View raw


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.)

Back to gnu.bash.bug | Previous | Next | Find similar


Thread

Re: (IMPORTANT/URGENT) Regarding Missing Files in bash source code? Greg Wooledge <wooledg@eeg.ccf.org> - 2020-07-17 10:20 -0400

csiph-web