Subject: Re: toolchain/33673: KSH settings break `build tools'
To: None <toolchain-manager@netbsd.org, gnats-admin@netbsd.org,>
From: Frederick Bruckman <fredb@immanent.net>
List: netbsd-bugs
Date: 06/10/2006 13:10:03
The following reply was made to PR toolchain/33673; it has been noted by GNATS.
From: Frederick Bruckman <fredb@immanent.net>
To: Oliver Gould <ogould@cs.stevens.edu>, gnats-bugs@NetBSD.org
Cc:
Subject: Re: toolchain/33673: KSH settings break `build tools'
Date: Sat, 10 Jun 2006 08:05:05 -0500 (CDT)
In article <20060609002001.0F28363BA6E@narn.netbsd.org>,
ogould@cs.stevens.edu writes:
>>Description:
> I am using KSH, and have options set as follows:
>
> $ set +o
> set -o interactive -o monitor -o nohup -o posix -o stdin -o vi -o
> vi-tabcomplete
>
> when trying to re-build tools with:
>
> $ ./build.sh -u -U -O obj tools
>
> I get the following behavior while building groff:
>
> checking for vi-tabcomplete-gs... no
> checking for vi-tabcomplete-gswin32c... no
> checking for vi-tabcomplete-gsos2... no
> [...]
> configure: creating ./config.status
> config.status: error: invalid argument: vi-tabcomplete
Oliver,
Shell options are not passed through to spawned processes. It must
be that your shell initializations are set up incorrectly. If you
share "~/.profile" or ${ENV} between "/bin/sh" and "/bin/ksh", you
need to protect the ksh-specific settings. E.g.:
# ksh only
#
if [ $0 = ksh -o $0 = -ksh -o $0 = /bin/ksh ]
then
set -o physical
set -o vi-tabcomplete
fi
Kind regards,
Frederick