From: "Jörg Krause" <joerg.krause@embedded.rocks>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] ubifs: Fix regression in ubifs_readdir()
Date: Mon, 07 Nov 2016 23:54:01 +0100 [thread overview]
Message-ID: <1478559241.1776.5.camel@embedded.rocks> (raw)
In-Reply-To: <d5f41448-c95c-54e3-69dc-ad3615580042@mind.be>
On Thu, 2016-11-03 at 11:22 +0100, Arnout Vandecappelle wrote:
>
> On 03-11-16 08:23, J?rg Krause wrote:
> > On Thu, 2016-11-03 at 03:46 +0100, Arnout Vandecappelle wrote:
> > >
> > > On 02-11-16 23:49, J?rg Krause wrote:
[snip]
> ?Since version.o differs, it means the version.o doesn't end up in
> the zImage...
> Again, can you check for the intermediate files what happens to them?
> E.g.
> init/built-in.o, .tmp_vmlinux1, arch/arm/boot/Image. Maybe just do
> "mv
> output/build/linux-custom output/build/linux-custom.orig" before
> rebuilding and
> do a full tree compare to find which files are identical.
Got it! ccache <3.3.3 is affected by bug concerning rebuilding the
kernel [1].
So, I guess we should update ccache.
[1] https://github.com/ccache/ccache/issues/136
Many thanks for your help!
prev parent reply other threads:[~2016-11-07 22:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1477648432-9543-1-git-send-email-richard@nod.at>
[not found] ` <1477671544.8927.1.camel@embedded.rocks>
[not found] ` <c542e099-0404-be8e-ebeb-d4265d3204d6@nod.at>
[not found] ` <1477693395.31471.1.camel@embedded.rocks>
2016-11-01 22:22 ` [Buildroot] [PATCH] ubifs: Fix regression in ubifs_readdir() Thomas Petazzoni
2016-11-02 19:56 ` Jörg Krause
2016-11-02 20:49 ` Thomas Petazzoni
2016-11-02 22:49 ` Jörg Krause
2016-11-03 2:46 ` Arnout Vandecappelle
2016-11-03 7:23 ` Jörg Krause
2016-11-03 10:22 ` Arnout Vandecappelle
2016-11-07 22:08 ` Jörg Krause
2016-11-07 22:24 ` Jörg Krause
2016-11-07 22:54 ` Jörg Krause [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1478559241.1776.5.camel@embedded.rocks \
--to=joerg.krause@embedded.rocks \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox