From: Kete <kete@ninthfloor.org>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: zsh-workers@zsh.org
Subject: Re: mkmakemod.sh 2nd stage build failure
Date: Sun, 05 Jan 2014 18:35:01 -0500 [thread overview]
Message-ID: <1913532.Wh84CtEVZ4@knossos> (raw)
In-Reply-To: <140105112141.ZM10617@torch.brasslantern.com>
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
prev parent reply other threads:[~2014-01-05 23:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-05 2:21 Kete
2014-01-05 19:21 ` Bart Schaefer
2014-01-05 20:10 ` Peter Stephenson
2014-01-05 23:35 ` Kete [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1913532.Wh84CtEVZ4@knossos \
--to=kete@ninthfloor.org \
--cc=schaefer@brasslantern.com \
--cc=zsh-workers@zsh.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).