Re: [OE-core] go-cross: incorrect dependency on tune-specific libgcc

On Tue, 2017-04-11 at 10:01 -0700, Khem Raj wrote: > On Tue, Apr 11, 2017 at 9:52 AM, Patrick Ohly wrote: > > On Tue, 2017-04-11 at 09:39 -0700, Khem Raj wrote: > >> I think TUNE_PKGARCH is the granularity it needs for setting GOARM > >> anyway. > > > > So you are saying

Re: [OE-core] go-cross: incorrect dependency on tune-specific libgcc

On Tue, Apr 11, 2017 at 9:57 AM, Richard Purdie wrote: > On Tue, 2017-04-11 at 09:39 -0700, Khem Raj wrote: >> On Tue, Apr 11, 2017 at 9:34 AM, Patrick Ohly > > wrote: >> > >> > On Mon, 2017-04-10 at 14:49 +0200, Patrick Ohly wrote: >>

Re: [OE-core] go-cross: incorrect dependency on tune-specific libgcc

On Tue, 2017-04-11 at 09:39 -0700, Khem Raj wrote: > On Tue, Apr 11, 2017 at 9:34 AM, Patrick Ohly > wrote: > > > > On Mon, 2017-04-10 at 14:49 +0200, Patrick Ohly wrote: > > > > > > Hello! > > > > > > I'm currently extending the yocto-compat-layer.py so that it can >

Re: [OE-core] go-cross: incorrect dependency on tune-specific libgcc

On Tue, Apr 11, 2017 at 9:52 AM, Patrick Ohly wrote: > On Tue, 2017-04-11 at 09:39 -0700, Khem Raj wrote: >> On Tue, Apr 11, 2017 at 9:34 AM, Patrick Ohly wrote: >> > On Mon, 2017-04-10 at 14:49 +0200, Patrick Ohly wrote: >> >> Hello! >> >> >> >>

Re: [OE-core] go-cross: incorrect dependency on tune-specific libgcc

On Tue, 2017-04-11 at 09:39 -0700, Khem Raj wrote: > On Tue, Apr 11, 2017 at 9:34 AM, Patrick Ohly wrote: > > On Mon, 2017-04-10 at 14:49 +0200, Patrick Ohly wrote: > >> Hello! > >> > >> I'm currently extending the yocto-compat-layer.py so that it can detect > >> invalid

Re: [OE-core] go-cross: incorrect dependency on tune-specific libgcc

On Tue, Apr 11, 2017 at 9:34 AM, Patrick Ohly wrote: > On Mon, 2017-04-10 at 14:49 +0200, Patrick Ohly wrote: >> Hello! >> >> I'm currently extending the yocto-compat-layer.py so that it can detect >> invalid signature changes when changing MACHINE. go-cross-x86_64 shows

Re: [OE-core] go-cross: incorrect dependency on tune-specific libgcc

On Mon, 2017-04-10 at 14:49 +0200, Patrick Ohly wrote: > Hello! > > I'm currently extending the yocto-compat-layer.py so that it can detect > invalid signature changes when changing MACHINE. go-cross-x86_64 shows > up as broken when comparing signatures for MACHINE=intel-corei7-64 and >

Re: [OE-core] go-cross: incorrect dependency on tune-specific libgcc

On Mon, 2017-04-10 at 09:16 -0400, Bruce Ashfield wrote: > Either way, I still have a problem when changes like this merge into > oe-core and I never know exactly when .. until I get the email of > people telling me that things are broken in meta-virt :D I'm not sure how to solve this. Now that

Re: [OE-core] go-cross: incorrect dependency on tune-specific libgcc

On Mon, Apr 10, 2017 at 9:09 AM, Patrick Ohly wrote: > On Mon, 2017-04-10 at 08:59 -0400, Bruce Ashfield wrote: > > > > > > On Mon, Apr 10, 2017 at 8:49 AM, Patrick Ohly > > wrote: > [...] > > diff --git a/meta/classes/go.bbclass

Re: [OE-core] go-cross: incorrect dependency on tune-specific libgcc

On Mon, 2017-04-10 at 08:59 -0400, Bruce Ashfield wrote: > > > On Mon, Apr 10, 2017 at 8:49 AM, Patrick Ohly > wrote: [...] > diff --git a/meta/classes/go.bbclass b/meta/classes/go.bbclass > index 85f71a2e9a6..ac41c80d377 100644 > ---

Re: [OE-core] go-cross: incorrect dependency on tune-specific libgcc

On Mon, Apr 10, 2017 at 8:49 AM, Patrick Ohly wrote: > Hello! > > I'm currently extending the yocto-compat-layer.py so that it can detect > invalid signature changes when changing MACHINE. go-cross-x86_64 shows > up as broken when comparing signatures for

[OE-core] go-cross: incorrect dependency on tune-specific libgcc

Hello! I'm currently extending the yocto-compat-layer.py so that it can detect invalid signature changes when changing MACHINE. go-cross-x86_64 shows up as broken when comparing signatures for MACHINE=intel-corei7-64 and MACHINE=qemux86-64. Both machines share the same go-cross-x86_64, but that