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:24:46 +0100 [thread overview]
Message-ID: <1478557486.1776.3.camel@embedded.rocks> (raw)
In-Reply-To: <1478556490.1776.1.camel@embedded.rocks>
On Mon, 2016-11-07 at 23:08 +0100, 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.
>
> I did the following:
>
> 1/ checkout linux-4.8 branch
> 2/ make linux-dirclean linux
> 3/ move output/build/linux-custom to output/build/linux-custom.orig
> 4/ checkout linux-4.7 branch
> 5/ make linux-dirclean linux
> 6/ diff:
>
> # diff output/build/linux-custom/arch/arm/boot/Image
> output/build/linux-custom.orig/arch/arm/boot/Image
> Binary files output/build/linux-custom/arch/arm/boot/Image and
> output/build/linux-custom.orig/arch/arm/boot/Image differ
> # diff output/build/linux-custom/arch/arm/boot/zImage
> output/build/linux-custom.orig/arch/arm/boot/zImage
>
> Weird, the Image binaries differ, but the zImage don't. The zImage in
> output/build/linux-custom/arch/arm/boot/ is exactly the same as in
> output/build/linux-custom.orig/arch/arm/boot/
After running the above steps I did the following:
7/ disable compiler cache option in Buildroot
8/ make linux-dirclean linux
9/ diff:
diff output/build/linux-custom/arch/arm/boot/zImage output/build/linux-
custom.orig/arch/arm/boot/zImage
Binary files hbm10/output/build/linux-custom/arch/arm/boot/zImage and
hbm10/output/build/linux-custom.orig/arch/arm/boot/zImage differ
10/ re-enable compiler cache in Buildroot
11/ Binary files hbm10/output/build/linux-custom/arch/arm/boot/zImage
and hbm10/output/build/linux-custom.orig/arch/arm/boot/zImage differ
12/ diff:
diff output/build/linux-custom/arch/arm/boot/zImage output/build/linux-
custom.orig/arch/arm/boot/zImage
(No message)
No idea!
J?rg
next prev parent reply other threads:[~2016-11-07 22:24 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-28 9:53 [PATCH] ubifs: Fix regression in ubifs_readdir() Richard Weinberger
2016-10-28 16:19 ` Jörg Krause
2016-10-28 16:19 ` Jörg Krause
2016-10-28 17:07 ` Richard Weinberger
2016-10-28 22:23 ` Jörg Krause
2016-10-28 22:23 ` Jörg Krause
2016-10-29 9:04 ` Richard Weinberger
2016-11-01 22:22 ` [Buildroot] " 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 [this message]
2016-11-07 22:54 ` Jörg Krause
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=1478557486.1776.3.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.