conf/179111: set -e no longer implicitly set after fmake -> bmake migration; build failures can "silently" occur at buildworld/SUBDIR level

[Garrett Cooper]

>Number:         179111
>Category:       conf
>Synopsis:       set -e no longer implicitly set after fmake -> bmake migration; build failures can "silently" occur at buildworld/SUBDIR level
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Thu May 30 16:00:00 UTC 2013
>Closed-Date:
>Last-Modified:
>Originator:     Garrett Cooper
>Release:        10-CURRENT
>Organization:
EMC Isilon
>Environment:
FreeBSD fuji-current.local 10.0-CURRENT FreeBSD 10.0-CURRENT #2 r+9eac8d9-dirty: Sun May 26 16:20:14 PDT 2013     root at fuji-current.local:/usr/obj/usr/src/sys/FUJI-NOCOMPAT  i386
>Description:
One of the issues that sjg noted in r250867 was the fact that bmake when compared with fmake doesn't implicitly set set -e when executing commands.

I have a patch for fixing many of the issues in .../Makefile, .../Makefile.inc, and bsd.*.mk that I'll cook up and submit soon.
>How-To-Repeat:

>Fix:


>Release-Note:
>Audit-Trail:
>Unformatted: