On 2017-06-01 06:32, Paul Eggleton wrote:
On Thursday, 1 June 2017 3:44:49 PM NZST Gary Thomas wrote:
On 2017-06-01 05:28, Paul Eggleton wrote:
It ought to be. At face value it should be finding the files in either
place - we'd need to debug the code to find out why it isn't. Is that
something
On Thursday, 1 June 2017 3:44:49 PM NZST Gary Thomas wrote:
> On 2017-06-01 05:28, Paul Eggleton wrote:
> > It ought to be. At face value it should be finding the files in either
> > place - we'd need to debug the code to find out why it isn't. Is that
> > something you might be able to help me wit
On 2017-06-01 05:28, Paul Eggleton wrote:
Hi Gary,
My apologies, I just realised I never sent this reply.
On Tuesday, 23 May 2017 5:27:57 PM NZST you wrote:
On 2017-05-22 22:35, Paul Eggleton wrote:
On Tuesday, 23 May 2017 2:53:45 AM NZST Gary Thomas wrote:
I have a build where I've never ma
Hi Gary,
My apologies, I just realised I never sent this reply.
On Tuesday, 23 May 2017 5:27:57 PM NZST you wrote:
> On 2017-05-22 22:35, Paul Eggleton wrote:
> > On Tuesday, 23 May 2017 2:53:45 AM NZST Gary Thomas wrote:
> >> I have a build where I've never manually removed anything from
> >> th
Hi Gary,
Have you tried to check those:
tmp/stamps/x86_64-linux/gcc-cross-arm/6.3.0-r0.do_prepare_recipe_sysroot.sigdata.c45aaef0cb01f463f9a1b30bd815cd28
tmp/stamps/x86_64-linux/gcc-cross-arm/6.3.0-r0.do_prepare_recipe_sysroot.sigdata.150112323551011e0e87f99f47ad79c4
with bitbake-diffsigs ? Mayb
On 2017-05-23 07:27, Gary Thomas wrote:
On 2017-05-22 22:35, Paul Eggleton wrote:
Hi Gary,
On Tuesday, 23 May 2017 2:53:45 AM NZST Gary Thomas wrote:
I have a build where I've never manually removed anything from
the sstate-cache and this same build has been used for hundreds
of builds over th
Hi,
@Gary
I guess the sstate-cache info alone is not sufficient to use 'bitbake diffsigs'?
Usage:
bitbake-diffsigs -t recipename taskname
bitbake-diffsigs sigdatafile1 sigdatafile2
bitbake-diffsigs sigdatafile1
Compares siginfo/sigdata files written out by BitBake
Options:
-h, --help
On 2017-05-22 22:35, Paul Eggleton wrote:
Hi Gary,
On Tuesday, 23 May 2017 2:53:45 AM NZST Gary Thomas wrote:
I have a build where I've never manually removed anything from
the sstate-cache and this same build has been used for hundreds
of builds over the last 18 months. I just tried to find o
Hi Gary,
On Tuesday, 23 May 2017 2:53:45 AM NZST Gary Thomas wrote:
> I have a build where I've never manually removed anything from
> the sstate-cache and this same build has been used for hundreds
> of builds over the last 18 months. I just tried to find out why
> gcc-cross-arm had to be rebuil
On 2017-05-22 16:53, Gary Thomas wrote:
I have a build where I've never manually removed anything from
the sstate-cache and this same build has been used for hundreds
^directory^
of builds over the last 18 months. I just tried to find out why
gcc-cross-arm had
I have a build where I've never manually removed anything from
the sstate-cache and this same build has been used for hundreds
of builds over the last 18 months. I just tried to find out why
gcc-cross-arm had to be rebuilt (it seems to happen almost every
time I update my Poky/Yocto tree (master)
11 matches
Mail list logo