[PATCH modular 8/8] build.sh: identify origin of error messages

[Gaetan Nadon]

In the fog of build output, it is not clear that some error messages
originate from the build.sh script. Many UNIX commands do so.

Sample output:
make: noexist: No such file or directory
make: *** No rule to make target `noexist'.  Stop.
build.sh: "make -f noexist" failed on app/xclock
build.sh: error processing module/component:  "app/xclock"

Signed-off-by: Gaetan Nadon <memsize at videotron.ca>
---
 build.sh |    4 ++--
 1 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/build.sh b/build.sh
index 3af85cf..51fe800 100755
--- a/build.sh
+++ b/build.sh
@@ -137,7 +137,7 @@ setup_buildenv() {
 # returns:
 #   (irrelevant)
 failed() {
-    echo "***** \"$1\" failed on $2/$3"
+    echo "build.sh: \"$1\" failed on $2/$3"
     failed_components="$failed_components $2/$3"
 }
 
@@ -515,7 +515,7 @@ build() {
 
     process $1 $2
     if [ $? -ne 0 ]; then
-	echo "error processing module/component:  \"$1/$2\""
+	echo "build.sh: error processing module/component:  \"$1/$2\""
 	if [ X"$NOQUIT" = X ]; then
 	    exit 1
 	fi
-- 
1.6.0.4