Subject: New Toolchain not enabled?
To: None <firstname.lastname@example.org>
From: Michael G. Schabert <email@example.com>
Date: 10/09/2002 13:40:16
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"
E_STRDUP=1 -DHAVE_STRERROR=1 -DHAVE_STRFTIME=1 -DHAVE_VSNPRINTF=1
RAP -I/usr/src/tools/make/../../usr.bin/make -c
cc -O -o nbmake *.o
ERROR: build.sh (new toolchain) is not yet enabled for
All builds for this platform should be done via a traditional make
If you wish to test using the new toolchain set
in either the environment or mk.conf and rerun
Given that I'm unaware of any issues WRT build.sh on alpha, it seems
kind of harsh for the error to state that "all builds for this
platform should be done via a traditional make"...that's
contradictory to any advice I've seen in these forums. Did an issue
come up, or is this just an oversight, or is there simply more
testing required before it is finalized?
Bikers don't *DO* taglines.