From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 10599 invoked by alias); 5 Jan 2014 23:35:13 -0000 Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Workers List List-Post: List-Help: X-Seq: 32237 Received: (qmail 14143 invoked from network); 5 Jan 2014 23:35:07 -0000 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham version=3.3.2 From: Kete To: Bart Schaefer Cc: zsh-workers@zsh.org Subject: Re: mkmakemod.sh 2nd stage build failure Date: Sun, 05 Jan 2014 18:35:01 -0500 Message-ID: <1913532.Wh84CtEVZ4@knossos> User-Agent: KMail/4.12 (Linux/3.5.0-40-generic; KDE/4.12.0; i686; ; ) In-Reply-To: <140105112141.ZM10617@torch.brasslantern.com> References: <2299435.9BvXCX229r@knossos> <140105112141.ZM10617@torch.brasslantern.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" On Sunday, January 05, 2014 11:21:41 AM Bart Schaefer wrote: > The -m and -i options of mkmakemod.sh are used by different parts of the > build process (see Src/Makemod.in.in) -- they aren't intended for the > caller of the build process to change it. > > The second stage has to be done at least once during the build, it can't > be avoided entirely. > Thanks for answering my questions about the second stage. > > Your better option here is to export a value for CONFIG_SHELL into the > environment before starting the build. There must be *some* shell > that is executing mkmakemod.sh itself; you just need set CONFIG_SHELL > to that path. (We can't guarantee that $SHELL is suitable.) The package manager maintainer saw my question and taught me how to replace instances of '/bin/sh' with the shell name, e.g., bash, to just call the command found in $PATH. Kind regards