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


Groups > gnu.bash.bug > #16572

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

Path csiph.com!xmission!news.snarked.org!news.linkpendium.com!news.linkpendium.com!panix!usenet.stanford.edu!not-for-mail
From Humanities Clinic <humanitiesclinic@gmail.com>
Newsgroups gnu.bash.bug
Subject Re: (IMPORTANT/URGENT) Regarding Missing Files in bash source code?
Date Fri, 17 Jul 2020 22:10:21 +0800
Lines 76
Approved bug-bash@gnu.org
Message-ID <mailman.380.1594995054.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>
NNTP-Posting-Host lists.gnu.org
Mime-Version 1.0
Content-Type text/plain; charset="UTF-8"
X-Trace usenet.stanford.edu 1594995055 1194 209.51.188.17 (17 Jul 2020 14:10:55 GMT)
X-Complaints-To action@cs.stanford.edu
To bash-maintainers@gnu.org, bug-bash@gnu.org, help-bash@gnu.org, wooledg@eeg.ccf.org
Envelope-to bug-bash@gnu.org
DKIM-Signature v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=y4dyRVIpBrjen9vWgOPmkcx21JuU+HZYXtLye6kucMI=; b=Y2oFGfaNqO27VJ7H8AYqqNIJy4moXgZZwPOm+ulszdz1N8XAN6rTMRTzSDvF/4pW78 e7HoSqJYLQbVW6ZLbkJJjM6g9U9eBOtZKnlRJIZBuglAfitzphb+rKYCNBlNKlKuPRHw CMhjscBmZ1AAZMuoB3FEVEeK7xFTFAP6Eruusa82qoW971EufeN4X/oqg3ObVcszwPMS eybxSLghgl4safZhb5/3m9f4K2GAvodlmb74l/rbb/vwOyD97RygLPChlk9tSNUzKyvH aSbXCukx4V6fy4ZG908uFwRHUt/bKcaRaBj56k15RwfqsAM/QdiiyqjCPhENYEAg7Mtr YFwQ==
X-Google-DKIM-Signature v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=y4dyRVIpBrjen9vWgOPmkcx21JuU+HZYXtLye6kucMI=; b=kT0qngQoUoX1fKLHbDp2tMfUby799BDYV4sej963MqQvKIU+8RdnMjJCnjXnwtaYh/ Q8x3TcLws1IKwBeHiEPKBMl+QGgZzZph9imvsAvsnIpOPTzCs+X2izH2P8uQ3WQVljn6 C8dxKKPljljbRXbc66Wp5IXEXLVJqMdop3nCKIYmOFO9r6GOBajEDZ51aApmJXS8hQtR nymfjwLy8FeXKYVeDcpMdzQalnZStzxeXe1BlNCiwLNrMPKti5iSDF6WSFejqWYdOcfN /9gWZcY79vSilU4w/hDkwS+b3LEuLjIVJbo6uMvmjAokyLuQ+3TbaP5+qq0AymH4aynH BGlQ==
X-Gm-Message-State AOAM531RngZ0m+GYjMJbMnvHqe6hdNBIBq1wsrzaMCc/wmxVBFx2mpxY Vn1CaD3u/3Mo3OR2xtycuUIQKx2mx+cn5HQa8JvL5Fas
X-Google-Smtp-Source ABdhPJzGuUVl9mHx3a3uwASi1rCgJ2E3MxG6hUzeheGmIq3y5D2cKYkLaEsgpkxSsUHghakHCHRm49KuTx8JP7PX3zU=
X-Received by 2002:a50:8f83:: with SMTP id y3mr9676256edy.257.1594995032817; Fri, 17 Jul 2020 07:10:32 -0700 (PDT)
In-Reply-To <20200624120450.GA22833@eeg.ccf.org>
Received-SPF pass client-ip=2a00:1450:4864:20::530; envelope-from=humanitiesclinic@gmail.com; helo=mail-ed1-x530.google.com
X-detected-operating-system by eggs.gnu.org: No matching host in p0f cache. That's all we know.
X-Spam_score_int -20
X-Spam_score -2.1
X-Spam_bar --
X-Spam_report (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001 autolearn=ham autolearn_force=no
X-Spam_action no action
X-Content-Filtered-By Mailman/MimeDel 2.1.23
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 <CAFoojOpSsak8H4K6nFL1z19WV5mRy9HTB5ujVNep=XKV5YoW_A@mail.gmail.com>
X-Mailman-Original-References <CAFoojOo6BXD77zTSMr+jRS5=FoxiuDZ57u4F-FqK3vVcMZmvJA@mail.gmail.com> <20200624120450.GA22833@eeg.ccf.org>
Xref csiph.com gnu.bash.bug:16572

Show key headers only | View raw


Ok noted.

By the way, I do have another related problem. Can you help me with it?

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

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.

Regards,
Chai

On Wed, Jun 24, 2020 at 8:04 PM Greg Wooledge <wooledg@eeg.ccf.org> wrote:

> On Wed, Jun 24, 2020 at 01:09:48PM +0800, Humanities Clinic wrote:
> > version.c:27:10: fatal error: 'version.h' file not found
>
> > jobs.c:72:10: fatal error: 'builtins/builtext.h' file not found
>
> > I double-checked the original folder in
> > http://ftp.gnu.org/gnu/bash/bash-3.2.57.tar.gz. It's true these files
> are
> > missing.
> >
> > May I know why is this so, and how this can be rectified?
>
> These files are generated during the build process.
>
> Did you run "./configure" (or some equivalent) before running "make"?
> Were there any errors during the configure stage?  Were there any
> earlier errors during the make stage?
>
> The version.h file in a bash-3.2 build tree should look something like
> this:
>
>
> /* Version control for the shell.  This file gets changed when you say
>    `make version.h' to the Makefile.  It is created by mkversion. */
>
> /* The distribution version number of this shell. */
> #define DISTVERSION "3.2"
>
> /* The last built version of this shell. */
> #define BUILDVERSION 1
>
> /* The release status of this shell. */
> #define RELSTATUS "release"
>
> /* A version string for use by sccs and the what command. */
> #define SCCSVERSION "@(#)Bash version 3.2.0(1) release GNU"
>
>
>
> During the make stage of the build, you should have seen something
> like this:
>
>
> /bin/sh ./support/mkversion.sh -b -S . -s release -d 3.2 -o newversion.h \
>         && mv newversion.h version.h
>
>
> If that step didn't occur, or if there was an error during it, then
> that would explain why your version.h file wasn't generated.
>

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


Thread

Re: (IMPORTANT/URGENT) Regarding Missing Files in bash source code? Humanities Clinic <humanitiesclinic@gmail.com> - 2020-07-17 22:10 +0800

csiph-web