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>
Cc: gnats-bugs@NetBSD.org
Subject: Re: toolchain/33673: KSH settings break `build tools'
Date: Sun, 11 Jun 2006 10:53:02 -0500 (CDT)

 On Sun, 11 Jun 2006, oliver gould wrote:
 
 > On Sat, Jun 10, 2006 at 08:05:05, Frederick Bruckman wrote:
 >
 >> 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.
 >
 > Thank you.  This does indeed fix the problem.
 >
 > Even though the options were being set in error, should they be
 > affecting the configure script like that?
 
 "configure" is probably mixing the error message in with the intended 
 output of some subshell. In general, your ${ENV} or "~/.shrc" must be 
 silent (at least in the non-interactive case) or very many complex 
 shell scripts will break.
 
 
 Frederick