9943 gfx-drm should use own bldenv copy

Reviewed by: Adam Števko  <[email protected]>
Reviewed by: Andy Fiddaman <[email protected]>

Author: pyhalov

Makefile

@@ -24,23 +24,23 @@ ONBLD_TOOLS=/opt/onbld
 # Do both debug and non-debug build in uts, in that order, so
 # (a) we know the debug code builds, and (b) install non-debug.
 install: FRC
-	$(ONBLD_TOOLS)/bin/bldenv myenv.sh \
+	/usr/bin/ksh93 tools/bldenv myenv.sh \
 	"cd usr/src ; $(MAKE) setup"
-	$(ONBLD_TOOLS)/bin/bldenv -d myenv.sh \
+	/usr/bin/ksh93 tools/bldenv -d myenv.sh \
 	"cd usr/src/uts ; $(MAKE) install"
-	$(ONBLD_TOOLS)/bin/bldenv myenv.sh \
+	/usr/bin/ksh93 tools/bldenv myenv.sh \
 	"cd usr/src ; $(MAKE) install"
 
 debug: FRC
-	$(ONBLD_TOOLS)/bin/bldenv -d myenv.sh \
+	/usr/bin/ksh93 tools/bldenv -d myenv.sh \
 	"cd usr/src ; $(MAKE) install"
 
 clean: FRC
-	$(ONBLD_TOOLS)/bin/bldenv myenv.sh \
+	/usr/bin/ksh93 tools/bldenv myenv.sh \
 	"cd usr/src ; $(MAKE) clobber"
 
 package: FRC
-	$(ONBLD_TOOLS)/bin/bldenv myenv.sh \
+	/usr/bin/ksh93 tools/bldenv myenv.sh \
 	"cd usr/src/pkg ; $(MAKE) install"
 
 FRC:

README

@@ -80,7 +80,7 @@ to check that your patches are in sync with edits.
 When doing incremental work in the gate, i.e. fixing
 compilation errors, it's handy to run an editor in a
 "bldenv" environment, as follows:
-	bldenv -d myenv.sh
+	ksh93 tools/bldenv -d myenv.sh
 
 That gets you a new shell, in which you can run an
 emacs if you like "meta-x compile", or whatever.