Re: mkmakemod.sh 2nd stage build failure

[Kete <kete@xxxxxxxxxxxxxx>]

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