From: Michael Neuling <mikey@neuling.org>
To: Gabriel Paubert <paubert@iram.es>
Cc: Michal Marek <mmarek@suse.cz>,
linux-kbuild@vger.kernel.org, Ben Hutchings <ben@decadent.org.uk>,
linux-kernel <linux-kernel@vger.kernel.org>,
Anton Blanchard <anton@samba.org>,
Leann Ogasawara <leann.ogasawara@canonical.com>,
linuxppc-dev <linuxppc-dev@lists.ozlabs.org>
Subject: [PATCH v2] deb-pkg: Add support for powerpc little endian
Date: Fri, 05 Sep 2014 17:55:18 +1000 [thread overview]
Message-ID: <1409903718.11359.30.camel@ale.ozlabs.ibm.com> (raw)
In-Reply-To: <20140905071344.GA16024@visitor2.iram.es>
On Fri, 2014-09-05 at 09:13 +0200, Gabriel Paubert wrote:
> On Fri, Sep 05, 2014 at 03:28:47PM +1000, Michael Neuling wrote:
> > The Debian powerpc little endian architecture is called ppc64le. This
>=20
> Huh? ppc64le or ppc64el?
ppc64el. Commit message is wrong. Fixed below.
Mikey
From: Michael Neuling <mikey@neuling.org>
deb-pkg: Add support for powerpc little endian
The Debian powerpc little endian architecture is called ppc64el. This
is the default architecture used by Ubuntu for powerpc.
The below checks the kernel config to see if we are compiling little
endian and sets the Debian arch appropriately.
Signed-off-by: Michael Neuling <mikey@neuling.org>
diff --git a/scripts/package/builddeb b/scripts/package/builddeb
index 35d5a58..6f4a1af 100644
--- a/scripts/package/builddeb
+++ b/scripts/package/builddeb
@@ -37,7 +37,7 @@ create_package() {
s390*)
debarch=3Ds390$(grep -q CONFIG_64BIT=3Dy $KCONFIG_CONFIG && echo x || tr=
ue) ;;
ppc*)
- debarch=3Dpowerpc ;;
+ debarch=3D$(grep -q CPU_LITTLE_ENDIAN=3Dy $KCONFIG_CONFIG && echo ppc64e=
l || echo powerpc) ;;
parisc*)
debarch=3Dhppa ;;
mips*)
next prev parent reply other threads:[~2014-09-05 7:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-05 5:28 deb-pkg: Add support for powerpc little endian Michael Neuling
2014-09-05 7:13 ` Gabriel Paubert
2014-09-05 7:55 ` Michael Neuling [this message]
2014-09-05 12:09 ` [PATCH v2] " Thadeu Lima de Souza Cascardo
2014-09-07 2:42 ` Ben Hutchings
2014-09-12 14:12 ` Michal Marek
2014-09-05 12:14 ` Josh Boyer
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=1409903718.11359.30.camel@ale.ozlabs.ibm.com \
--to=mikey@neuling.org \
--cc=anton@samba.org \
--cc=ben@decadent.org.uk \
--cc=leann.ogasawara@canonical.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mmarek@suse.cz \
--cc=paubert@iram.es \
/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).