From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Randy Dunlap <rdunlap@infradead.org>,
linux-kbuild <linux-kbuild@vger.kernel.org>
Cc: Paul Mackerras <paulus@samba.org>,
Michael Ellerman <mpe@ellerman.id.au>,
Stephen Rothwell <sfr@canb.auug.org.au>,
linuxppc-dev@lists.ozlabs.org
Subject: Re: powerpc: 32BIT vs. 64BIT (PPC32 vs. PPC64)
Date: Sat, 07 Jul 2018 11:45:03 +1000 [thread overview]
Message-ID: <a3c9b9ee9ec116390c47dca65fcf14f138eccd3f.camel@kernel.crashing.org> (raw)
In-Reply-To: <3f906b03-98ff-c081-4e19-b490f0b35c51@infradead.org>
On Thu, 2018-07-05 at 14:30 -0700, Randy Dunlap wrote:
> Hi,
>
> Is there a good way (or a shortcut) to do something like:
>
> $ make ARCH=powerpc O=PPC32 [other_options] allmodconfig
> to get a PPC32/32BIT allmodconfig
>
> and also be able to do:
>
> $make ARCH=powerpc O=PPC64 [other_options] allmodconfig
> to get a PPC64/64BIT allmodconfig?
Hrm... O= is for the separate build dir, so there much be something
else.
You mean having ARCH= aliases like ppc/ppc32 and ppc64 ?
That would be a matter of overriding some .config defaults I suppose, I
don't know how this is done on other archs.
I see the aliasing trick in the Makefile but that's about it.
> Note that arch/x86, arch/sh, and arch/sparc have ways to do
> some flavor(s) of this (from Documentation/kbuild/kbuild.txt;
> sh and sparc based on a recent "fix" patch from me):
I fail to see what you are actually talking about here ... sorry. Do
you have concrete examples on x86 or sparc ? From what I can tell the
"i386" or "sparc32/sparc64" aliases just change SRCARCH in Makefile and
32 vs 64-bit is just a Kconfig option...
> x86: i386 for 32 bit, x86_64 for 64 bit
> sh: sh for 32 bit, sh64 for 64 bit
> sparc: sparc32 for 32 bit, sparc64 for 64 bit
next prev parent reply other threads:[~2018-07-07 1:45 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-05 21:30 powerpc: 32BIT vs. 64BIT (PPC32 vs. PPC64) Randy Dunlap
2018-07-07 1:45 ` Benjamin Herrenschmidt [this message]
2018-07-07 4:58 ` Randy Dunlap
2018-07-07 12:13 ` Nicholas Piggin
2018-07-07 14:59 ` Randy Dunlap
2018-07-08 15:44 ` Nicholas Piggin
2018-07-30 8:42 ` Masahiro Yamada
2018-07-31 9:57 ` Michael Ellerman
2018-07-09 11:51 ` Michael Ellerman
2018-07-08 11:51 ` Michael Ellerman
2018-07-08 15:46 ` Randy Dunlap
2018-07-09 12:00 ` Mathieu Malaterre
2018-07-13 11:41 ` CONFIG_ANDROID_BINDER_IPC=y (Re: powerpc: 32BIT vs. 64BIT (PPC32 vs. PPC64)) Mathieu Malaterre
2018-07-13 23:24 ` Randy Dunlap
2018-07-20 17:28 ` Randy Dunlap
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=a3c9b9ee9ec116390c47dca65fcf14f138eccd3f.camel@kernel.crashing.org \
--to=benh@kernel.crashing.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=paulus@samba.org \
--cc=rdunlap@infradead.org \
--cc=sfr@canb.auug.org.au \
/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).