From: Nicholas Piggin <npiggin@gmail.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
linux-kbuild <linux-kbuild@vger.kernel.org>,
Paul Mackerras <paulus@samba.org>,
linuxppc-dev@lists.ozlabs.org,
Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Re: powerpc: 32BIT vs. 64BIT (PPC32 vs. PPC64)
Date: Mon, 9 Jul 2018 01:44:14 +1000 [thread overview]
Message-ID: <20180709012328.203993bb@roar.ozlabs.ibm.com> (raw)
In-Reply-To: <c0a17b80-6384-7437-045c-3688d9e5e7f9@infradead.org>
On Sat, 7 Jul 2018 07:59:49 -0700
Randy Dunlap <rdunlap@infradead.org> wrote:
> On 07/07/2018 05:13 AM, Nicholas Piggin wrote:
> > On Fri, 6 Jul 2018 21:58:29 -0700
> > Randy Dunlap <rdunlap@infradead.org> wrote:
> >
> >> On 07/06/2018 06:45 PM, Benjamin Herrenschmidt wrote:
> >>> 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 ?
> >>
> >> Yes.
> >>
> >>> 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...
> >>
> >> Yes, your summary is mostly correct.
> >>
> >> I'm just looking for a way to do cross-compile builds that are close to
> >> ppc32 allmodconfig and ppc64 allmodconfig.
> >
> > Would there a problem with adding ARCH=ppc32 / ppc64 matching? This
> > seems to work...
> >
> > Thanks,
> > Nick
>
> Yes, this mostly works and is similar to a patch (my patch) on my test machine.
> And they both work for allmodconfig, which is my primary build target.
>
> And they both have one little quirk that is confusing when the build target
> is defconfig:
>
> When ARCH=ppc32, the terminal output (stdout) is: (using O=PPC32)
>
> make[1]: Entering directory '/home/rdunlap/lnx/lnx-418-rc3/PPC32'
> GEN ./Makefile
> *** Default configuration is based on 'ppc64_defconfig' <<<<< NOTE <<<<<
> #
> # configuration written to .config
> #
> make[1]: Leaving directory '/home/rdunlap/lnx/lnx-418-rc3/PPC32'
>
>
> I expect that can be fixed also. :)
It can, we'd just have to choose one of the many 32-bit configs to be
the default config in that case. I don't know much about 32 bit ppc,
so I don't know what would be the most useful for allmodconfig type of
build tests.
Even 64 bit have a bunch of major variants that are exclusive at build
time (Server vs embedded, endian, etc). So maybe the simple ppc64/ppc32
is not enough. Not sure.
Thanks,
Nick
next prev parent reply other threads:[~2018-07-08 15:44 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
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 [this message]
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=20180709012328.203993bb@roar.ozlabs.ibm.com \
--to=npiggin@gmail.com \
--cc=benh@kernel.crashing.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--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).