build.sh: identify origin of error messages
commitdeedde8dac7d80422d290ecf3fa46046c8cd61a4
authorGaetan Nadon <memsize@videotron.ca>
Tue, 4 Jan 2011 20:13:04 +0000 (4 15:13 -0500)
committerGaetan Nadon <memsize@videotron.ca>
Wed, 5 Jan 2011 20:16:31 +0000 (5 15:16 -0500)
treeb5191e52e52765837b238abe62ceffb3cb6b6631
parent6c694409cafe428630bc7cf467fc3cd979aa7eb7
build.sh: identify origin of error messages

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@videotron.ca>
build.sh