Path: csiph.com!goblin2!goblin1!goblin.stu.neva.ru!usenet.stanford.edu!not-for-mail From: Greg Wooledge Newsgroups: gnu.bash.bug Subject: Re: (IMPORTANT/URGENT) Regarding Missing Files in bash source code? Date: Wed, 24 Jun 2020 08:04:50 -0400 Lines: 49 Approved: bug-bash@gnu.org Message-ID: References: <20200624120450.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 1593000297 21446 209.51.188.17 (24 Jun 2020 12:04:57 GMT) X-Complaints-To: action@cs.stanford.edu Cc: bash-maintainers@gnu.org, bug-bash@gnu.org, help-bash@gnu.org To: Humanities Clinic Envelope-to: bug-bash@gnu.org Mail-Followup-To: Humanities Clinic , bash-maintainers@gnu.org, bug-bash@gnu.org, help-bash@gnu.org Content-Disposition: inline In-Reply-To: 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/06/24 08:04:51 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, URIBL_BLOCKED=0.001 autolearn=_AUTOLEARN 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-Mailman-Original-Message-ID: <20200624120450.GA22833@eeg.ccf.org> X-Mailman-Original-References: Xref: csiph.com gnu.bash.bug:16453 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.