Path: csiph.com!goblin2!goblin1!goblin.stu.neva.ru!usenet.stanford.edu!not-for-mail From: Michael Felt Newsgroups: gnu.bash.bug Subject: Re: make distclean and bash-4.4 - FYI Date: Thu, 1 Nov 2018 12:43:22 +0200 Lines: 34 Approved: bug-bash@gnu.org Message-ID: References: <4631d44f-ecec-d119-96db-982c9dcfad06@felt.demon.nl> NNTP-Posting-Host: lists.gnu.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Trace: usenet.stanford.edu 1541069027 6137 208.118.235.17 (1 Nov 2018 10:43:47 GMT) X-Complaints-To: action@cs.stanford.edu To: chet.ramey@case.edu, bug-bash@gnu.org Envelope-to: bug-bash@gnu.org Content-Language: en-US X-Enigmail-Draft-Status: N11100 Fcc: imap://aixtools@felt-1.demon.nl/Sent In-Reply-To: X-Identity-Key: id3 X-Account-Key: account4 X-Mailer: iPhone Mail (15E216) User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 X-Mozilla-Draft-Info: internal/draft; vcard=0; receipt=0; DSN=0; uuencode=0; attachmentreminder=0; deliveryformat=4 X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 80.101.98.107 X-Content-Filtered-By: Mailman/MimeDel 2.1.21 X-BeenThere: bug-bash@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Bug reports for the GNU Bourne Again SHell List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Xref: csiph.com gnu.bash.bug:14756 > On 10/31/2018 9:24 PM, Chet Ramey wrote: >> On 10/31/18 3:03 PM, Michael Felt wrote: >> Hi, >> >> I finally got around to patching and packaging bash-4.4.23 and had to >> run a "make distclean" because I had copied the old version and without >> the make distclean make kept looking for "bashversion" in the old path >> .../bash-4.4.19/bashversion > The build directory is written to the Makefile so the build artifacts > (like bashversion) get removed from the right place. This is how you > support multiple build directories from a single source directory, for > instance. > >> This is just FYI - I'll install yacc, which is what make is complaining >> about now - but I also wonder if I could have avoided this by trying to >> build oot (out of tree). Is this supported, or even recommended? > You should install bison, not yacc, otherwise you'll run into problems > resulting from yacc's inability to support recursive parsers. And yes, > a build directory separate from the source directory is the recommended > configuration. If I "must", I shall build and install yacc. However, my hope is that: a) I won't need either after I create a source-directory, and build oot b) I prefer to work, as much as possible, from platform supplied tools. Thanks for the extra info. > >> Thanks for a great product! > Thanks for your kind words. > > Chet >