Based on the messages, it seems to be multiconfig related.

Well, I get the warnings/errors w/o multiconfig as well:

$ BBMULTICONFIG="" MACHINE=arduino-101-sss bitbake heartrate-monitor

WARNING: /data/master-master/poky/meta/recipes-extended/go-examples/go-helloworld_0.1.bb: Exception during build_dependencies for GOARCH        | ETA:  0:00:01
WARNING: /data/master-master/poky/meta/recipes-extended/go-examples/go-helloworld_0.1.bb: Error during finalise of /data/master-master/poky/meta/recipes-extended/go-examples/go-helloworld_0.1.bb
WARNING: /data/master-master/poky/meta/recipes-extended/ghostscript/ghostscript_9.20.bb: Unable to get checksum for ghostscript SRC_URI entry objarch.h: file could not be found
WARNING: /data/master-master/poky/meta/recipes-devtools/go/go_1.8.bb: Exception during build_dependencies for GOARCH                            | ETA:  0:00:01
WARNING: /data/master-master/poky/meta/recipes-devtools/go/go_1.8.bb: Error during finalise of /data/master-master/poky/meta/recipes-devtools/go/go_1.8.bb
WARNING: /data/master-master/poky/meta/recipes-devtools/go/go_1.6.bb: Exception during build_dependencies for GOARCH
WARNING: /data/master-master/poky/meta/recipes-devtools/go/go_1.6.bb: Error during finalise of /data/master-master/poky/meta/recipes-devtools/go/go_1.6.bb
WARNING: /data/master-master/poky/meta/recipes-devtools/go/go_1.7.bb: Exception during build_dependencies for GOARCH
WARNING: /data/master-master/poky/meta/recipes-devtools/go/go_1.7.bb: Error during finalise of /data/master-master/poky/meta/recipes-devtools/go/go_1.7.bb
WARNING: /data/master-master/poky/meta/recipes-devtools/go/go_1.6.bb: Exception during build_dependencies for GOARCH
WARNING: /data/master-master/poky/meta/recipes-devtools/go/go_1.6.bb: Error during finalise of virtual:cross:/data/master-master/poky/meta/recipes-devtools/go/go_1.6.bb
WARNING: /data/master-master/poky/meta/recipes-devtools/go/go-cross_1.7.bb: Exception during build_dependencies for GOARCH
WARNING: /data/master-master/poky/meta/recipes-devtools/go/go-cross_1.7.bb: Error during finalise of /data/master-master/poky/meta/recipes-devtools/go/go-cross_1.7.bb
WARNING: /data/master-master/poky/meta/recipes-devtools/go/go-cross_1.8.bb: Exception during build_dependencies for GOARCH
WARNING: /data/master-master/poky/meta/recipes-devtools/go/go-cross_1.8.bb: Error during finalise of /data/master-master/poky/meta/recipes-devtools/go/go-cross_1.8.bb

Penang team tried to reproduce the issue with meta-zephyr but failed to reproduce.

We have the following configuration and bitbake zehpyr-ipm shows no error.
MACHINE="arduino-101"
DISTRO="zephyr"
IMAGE_INSTALL="go go-helloworld go-example"

However, we seen gcc configuration issue when we "bitbake go" with the configuration above. Please refer to the error log below:
http://pastebin.intel.com/ehoyobawod.hs

(In reply to comment #3)
> Penang team tried to reproduce the issue with meta-zephyr but failed to
> reproduce.
> 
> We have the following configuration and bitbake zehpyr-ipm shows no error.
> MACHINE="arduino-101"
> DISTRO="zephyr"
> IMAGE_INSTALL="go go-helloworld go-example"
> 
> However, we seen gcc configuration issue when we "bitbake go" with the
> configuration above. Please refer to the error log below:
> http://pastebin.intel.com/ehoyobawod.hs

You've shown a build failure above however we'd no expect gcc-runtime to work on an RTOS like Zehyr so this isn't surprising. Did you see warnings during the parse of the layer (bitbake -p)? Did you try a target like the ones Juro used when it failed (bitbake zephyr-ipm, bitbake heartrate-monitor)?

A community member ran into this issue today and I believe may post a patch against bitbake to solve these warnings. It looks like we need to allow the SkipRecipe exception to pass through certain exception handlers.

you need to set 
DISTRO="zephyr"

in local.conf

Clarifying how to reproduce this failure:

clone poky master and meta-zephyr
add meta-zephyr to bblayers.conf
change DISTRO to zephyr

simply building:
MACHINE=arduino-101-sss bitbake zephyr-ipm

will produce the failure.

I added a bb.note in goarch.bbclass to verify what arch is being passed in, arduino-101 is i586, while arduino-101-sss is "arc" and that's where the unknown architecture comes from.

Patch is available on bitbake list
http://lists.openembedded.org/pipermail/bitbake-devel/2017-April/008622.html

Also, it has to be a clean build. To reproduce it again, you need to wipe tmp folder.

(In reply to comment #6)
> Clarifying how to reproduce this failure:
> 
> clone poky master and meta-zephyr
> add meta-zephyr to bblayers.conf
> change DISTRO to zephyr
> 
> simply building:
> MACHINE=arduino-101-sss bitbake zephyr-ipm
> 
> will produce the failure.
> 
> I added a bb.note in goarch.bbclass to verify what arch is being passed in,
> arduino-101 is i586, while arduino-101-sss is "arc" and that's where the
> unknown architecture comes from.
> 
> Patch is available on bitbake list
> http://lists.openembedded.org/pipermail/bitbake-devel/2017-April/008622.html

Yes, I tried with MACHINE=arduino-101 that's why I did not see the WARNINGS. I checked again on MACHINE=arduino-101-sss and saw the message already. Thanks for clarifying.

Tested with patch from http://lists.openembedded.org/pipermail/bitbake-devel/2017-April/008622.html

DISTRO="zephyr"
Added meta-zephyr and executed "MACHINE=arduino-101-sss bitbake zephyr-ipm"

Still seeing the WARNINGS below:

WARNING: /media/rebeccas/yocto/poky/meta/recipes-extended/ghostscript/ghostscript_9.20.bb: Unable to get checksum for ghostscript SRC_URI entry objarch.h: file could not be found

(In reply to comment #9)
> Tested with patch from
> http://lists.openembedded.org/pipermail/bitbake-devel/2017-April/008622.html
> 
> DISTRO="zephyr"
> Added meta-zephyr and executed "MACHINE=arduino-101-sss bitbake zephyr-ipm"
> 
> Still seeing the WARNINGS below:
> 
> WARNING:
> /media/rebeccas/yocto/poky/meta/recipes-extended/ghostscript/ghostscript_9.
> 20.bb: Unable to get checksum for ghostscript SRC_URI entry objarch.h: file
> could not be found

Rebecca, this is a different issue, (probably merits a bug report of its own). 
The important thing here is to get rid of the "go" warnings/error messages.

Also, please make sure the "go" warnings are still gone even for a clean build.
A repeated build may not re-issue previous warnings.

(In reply to comment #10)
> Rebecca, this is a different issue, (probably merits a bug report of its
> own). 
> The important thing here is to get rid of the "go" warnings/error messages.
> 
> Also, please make sure the "go" warnings are still gone even for a clean
> build.
> A repeated build may not re-issue previous warnings.

Yes. Confirmed that the warning messages for "go" are not seen with the patch.

Patch from Nathan Rossi was merged into bitbake:
Bitbake rev: edf6e6094a9f7ad4b2ba06eef8fd34756edbedce

and poky:
Poky rev: bf0fc2da669745d4a55101177a07b00ba9ac3c7d

Verified patch resolved the issue.

Verification should done by QA. 

I have done developer verification test on this.