go: skip recipe instead of throwing fatal error on unknown architectures

Current code means that layer which contains a golang recipe cannot be
even parsed for machine which is not in supported golang architectures.

Skipping the golang recipes instead of throwing fatal error is much
friendlier and let machines without golang support co-exist in a layer
with golang recipes.

Signed-off-by: Peter Marko <peter.marko@siemens.com>
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>

diff --git a/meta/lib/oe/go.py b/meta/lib/oe/go.py
index 4559dc63b285d383f6024a7ad1013e0a040143d3..cbcf80f0b11ec46189be47bb2a6cfecefbc49249 100644 (file)
--- a/meta/lib/oe/go.py
+++ b/meta/lib/oe/go.py
@@ -35,4 +35,4 @@ def map_arch(a):
         return 'riscv64'
     elif a == 'loongarch64':
         return 'loong64'
-    raise KeyError(f"Cannot map architecture {a}")
+    raise bb.parse.SkipRecipe(f"Cannot map architecture {a}")