On Wed, Oct 09, 2002 at 01:40:16PM -0400, Michael G. Schabert wrote:
> Is there a reason that the build.sh is not enabled on alpha by 
> default? Also, wouldn't it be prudent to put that check at the 
> beginning of the process? As it stands now, without explicitly 
> enabling the new toolchain, a build attempt fails like this:
> 
> =====
> ===> Bootstrapping nbmake
> checking for sh... /bin/sh
> checking for gcc... cc
> .
> .
> .
> cc  -O -D_PATH_BSHELL="/bin/sh" -D_PATH_DEFSHELLDIR="/bin" 
> -DHAVE_SETENV=1 -DHAV
> E_STRDUP=1 -DHAVE_STRERROR=1 -DHAVE_STRFTIME=1 -DHAVE_VSNPRINTF=1 
> -DMAKE_BOOTST
> RAP -I/usr/src/tools/make/../../usr.bin/make -c 
> /usr/src/tools/make/../../usr.bi
> n/make/lst.lib/lstSucc.c
> cc  -O -o nbmake *.o
> ERROR: build.sh (new toolchain) is not yet enabled for
> 
> MACHINE: alpha
> MACHINE_ARCH: alpha
> 
> All builds for this platform should be done via a traditional make
> 
> If you wish to test using the new toolchain set
> 
> USE_NEW_TOOLCHAIN=yes
> 
> in either the environment or mk.conf and rerun
> =====

Are you sure your source tree is completely up to date ?
USE_NEW_TOOLCHAIN has been removed a few days ago (as all platforms are
now using the new toolchain).

-- 
Manuel Bouyer <bouyer@antioche.eu.org>
--