From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: Build failure with verify size in next-20171102
Date: Thu, 2 Nov 2017 12:30:27 -0700 [thread overview]
Message-ID: <20171102193027.GB28152@atomide.com> (raw)
Hi Russeell,
I think you're already aware of the build failure caused by commit
078c0927485e ("ARM: verify size of zImage"), but here's info just
in case.
arm-unknown-linux-musleabi-ld.bfd: error: zImage file size is incorrect
make[2]: *** [arch/arm/boot/compressed/Makefile:185: arch/arm/boot/compressed/vmlinux] Error 1
make[1]: *** [arch/arm/boot/Makefile:64: arch/arm/boot/compressed/vmlinux] Error 2
make: *** [arch/arm/Makefile:335: zImage] Error 2
Other than that I was surprised that next actually booted for me
after a few week break with Linux next! :)
Regards,
Tony
next reply other threads:[~2017-11-02 19:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-02 19:30 Tony Lindgren [this message]
2017-11-02 23:20 ` Build failure with verify size in next-20171102 Russell King - ARM Linux
2017-11-02 23:43 ` Tony Lindgren
2017-11-03 0:04 ` Russell King - ARM Linux
2017-11-03 0:14 ` Russell King - ARM Linux
2017-11-03 8:22 ` Ard Biesheuvel
2017-11-03 9:12 ` Russell King - ARM Linux
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=20171102193027.GB28152@atomide.com \
--to=tony@atomide.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).