I recently tried upgrading from 3.1.0 to 3.1.1. I'm not sure if this is a bug
or just my problem. I maintain five different architectures and all five have
the same failure in gcc-sanitizers as I'm trying to build the SDK.
| cat:
/data/mabnhdev/exos-yocto-dunfell/build/exos-arm64/tmp/work-sha
On 6/30/20 2:56 PM, MikeB wrote:
I recently tried upgrading from 3.1.0 to 3.1.1. I'm not sure if this is
a bug or just my problem. I maintain five different architectures and
all five have the same failure in gcc-sanitizers as I'm trying to build
the SDK.
| cat:
/data/mabnhdev/exos-yocto
On Tue, Jun 30, 2020 at 4:56 PM MikeB wrote:
>
> I recently tried upgrading from 3.1.0 to 3.1.1. I'm not sure if this is a
> bug or just my problem. I maintain five different architectures and all five
> have the same failure in gcc-sanitizers as I'm trying to build the SDK.
>
> | cat:
> /dat
On Tue, Jun 30, 2020 at 8:08 PM Joshua Watt wrote:
>
> On Tue, Jun 30, 2020 at 4:56 PM MikeB wrote:
> >
> > I recently tried upgrading from 3.1.0 to 3.1.1. I'm not sure if this is a
> > bug or just my problem. I maintain five different architectures and all
> > five have the same failure in g
On Tue, Jun 30, 2020 at 4:53 PM Joshua Watt wrote:
>
> On Tue, Jun 30, 2020 at 8:08 PM Joshua Watt wrote:
> >
> > On Tue, Jun 30, 2020 at 4:56 PM MikeB wrote:
> > >
> > > I recently tried upgrading from 3.1.0 to 3.1.1. I'm not sure if this is
> > > a bug or just my problem. I maintain five di
On Tue, Jun 30, 2020 at 5:08 PM Steve Sakoman via
lists.yoctoproject.org
wrote:
>
> On Tue, Jun 30, 2020 at 4:53 PM Joshua Watt wrote:
> >
> > On Tue, Jun 30, 2020 at 8:08 PM Joshua Watt wrote:
> > >
> > > On Tue, Jun 30, 2020 at 4:56 PM MikeB wrote:
> > > >
> > > > I recently tried upgrading f
The combination of the
https://lists.openembedded.org/g/openembedded-core/message/140161 and
a 'bitbake
-ccleansstate on gcc-source-9.3.0' has gotten me back on track.
Thank you all for the help!
On Tue, Jun 30, 2020 at 11:10 PM Steve Sakoman wrote:
> On Tue, Jun 30, 2020 at 5:08 PM Steve Sakom
The rumors of my success were exaggerated. If performing a fresh build
from scratch, the image build succeeds, but the populate_sdk still fails as
in the original post. If I then do a 'bitbake -ccleansstate on
gcc-source-9.3.0', the populate_sdk succeeds.
Mike
On Wed, Jul 1, 2020 at 6:45 AM Mik
On Wed, Jul 1, 2020 at 9:47 AM MikeB wrote:
>
> The rumors of my success were exaggerated. If performing a fresh build from
> scratch, the image build succeeds, but the populate_sdk still fails as in the
> original post. If I then do a 'bitbake -ccleansstate on gcc-source-9.3.0',
> the popula
Yes, I am using the archiver.bbclass. However, I'm using the one in
poky/meta. I applied your patch (manually) to that one.
diff --git a/meta/classes/archiver.bbclass b/meta/classes/archiver.bbclass
index a8d3afcbe9..bf275f4543 100644
--- a/meta/classes/archiver.bbclass
+++ b/meta/classes/archiv
10 matches
Mail list logo