libgcc gets compiled differently depending on the tune flags for the target. That dependency would make go-cross also tune specific and prevent sharing it between different machines using the same architecture.
For example, MACHINE=intel-corei7-64 and MACHINE=qemux86-64 shared the same go-cross-x86_64, but compiled libgcc differently. The libgcc dependency gets inherited from go.inc, but does not seem to be necessary for go-cross (compiling go-helloworld still succeeds). The dependency is left in go.inc just in case that it is relevant for the various on-target recipes which inherit that. Signed-off-by: Patrick Ohly <patrick.o...@intel.com> --- meta/recipes-devtools/go/go-cross.inc | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/meta/recipes-devtools/go/go-cross.inc b/meta/recipes-devtools/go/go-cross.inc index 68f5efd..9b49738 100644 --- a/meta/recipes-devtools/go/go-cross.inc +++ b/meta/recipes-devtools/go/go-cross.inc @@ -4,6 +4,10 @@ DEPENDS += "gcc-cross-${TARGET_ARCH}" PN = "go-cross-${TARGET_ARCH}" +# go-cross is built once per target architecture, and thus must not +# depend on the tune-specific libgcc. +DEPENDS_remove = "libgcc" + FILESEXTRAPATHS =. "${FILE_DIRNAME}/go-cross:" GOROOT_FINAL = "${libdir}/go" -- git-series 0.9.1 -- _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core