From: Adam Borowski <kilobyte@angband.pl>
To: stable@vger.kernel.org
Subject: [CHERRY-PICK 4.9] builddeb: fix cross-building to arm64 producing host-arch debs
Date: Sun, 18 Dec 2016 14:20:09 +0100 [thread overview]
Message-ID: <20161218132009.GA23607@angband.pl> (raw)
Hi!
Please pick 152b695d for 4.9 (only), it fixes cross-compilation to arm64.
It was reported on Nov 04, acked on Nov 10, accepted into kbuild/rc-fixes
on Nov 24 but somehow not pushed to Linus; it got into mainline only during
the merge window.
As 4.9 is to be used in Debian stretch, {bin,}deb-pkg is going to see quite
a lot of use, especially that kernel-package is mostly kaputt.
Paraphrased diff:
+++ scripts/package/builddeb
case "$UTS_MACHINE" in
[...]
- arm64)
+ aarch64|arm64)
(Only "aarch64" being actually needed, "arm64" is left as defense in case
this flips again.)
Meow!
--
Autotools hint: to do a zx-spectrum build on a pdp11 host, type:
./configure --host=zx-spectrum --build=pdp11
next reply other threads:[~2016-12-18 13:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-18 13:20 Adam Borowski [this message]
2017-01-04 17:40 ` [CHERRY-PICK 4.9] builddeb: fix cross-building to arm64 producing host-arch debs Greg KH
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=20161218132009.GA23607@angband.pl \
--to=kilobyte@angband.pl \
--cc=stable@vger.kernel.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).