From: Michael Ellerman <mpe@ellerman.id.au>
To: Jim Davis <jim.epost@gmail.com>
Cc: Christophe JAILLET <christophe.jaillet@wanadoo.fr>,
imunsie@au1.ibm.com, fbarrat@linux.vnet.ibm.com,
kernel-janitors@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] cxl: Fix error handling
Date: Wed, 02 Nov 2016 22:12:50 +1100 [thread overview]
Message-ID: <87eg2unnil.fsf@concordia.ellerman.id.au> (raw)
In-Reply-To: <CA+r1ZhiJW6xQ1VwgLudFzFBxkKzkURv7MZhWtmSevRHc9aUyxA@mail.gmail.com>
Jim Davis <jim.epost@gmail.com> writes:
> On Sun, Oct 30, 2016 at 10:37 PM, Michael Ellerman <mpe@ellerman.id.au> wrote:
>> More here:
>>
>> https://github.com/linuxppc/linux/wiki/Building-powerpc-kernels
>
> Cool; the little-endian build worked fine, but
Yay, thanks for trying.
> jim@krebstar:~/linux-rc$ make ARCH=powerpc
> CROSS_COMPILE=powerpc64-linux-gnu- vmlinux
> make: powerpc64-linux-gnu-gcc: Command not found
> make: powerpc64-linux-gnu-gcc: Command not found
> scripts/kconfig/conf --silentoldconfig Kconfig
> make: powerpc64-linux-gnu-gcc: Command not found
Ah sorry.
> This is on Ubuntu 16.04; there's a /usr/bin/powerpc64le-linux-gnu-gcc
> from installing gcc-powerpc64le-linux-gnu, and a
> /usr/bin/powerpc-linux-gnu-gcc from installing gcc-powerpc-linux-gnu,
> but no /usr/bin/powerpc64-linux-gnu-gcc.
It's the powerpc-linux-gnu-gcc one.
That is a 32 and 64-bit compiler, it's 32-bit by default, but the kernel
Makefiles will pass -m64 appropriately.
You can actually build a single compiler that builds 32/64-bit BE, and
64-bit LE, but the distros don't do that for whatever reason.
cheers
next prev parent reply other threads:[~2016-11-02 11:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-30 21:40 [PATCH] cxl: Fix error handling Christophe JAILLET
2016-10-31 5:37 ` Michael Ellerman
2016-11-01 23:36 ` Jim Davis
2016-11-02 11:12 ` Michael Ellerman [this message]
2016-11-02 19:01 ` Jim Davis
2016-11-03 9:55 ` Michael Ellerman
2016-10-31 6:27 ` Andrew Donnellan
2016-11-02 16:50 ` Frederic Barrat
2016-11-16 1:56 ` Ian Munsie
2016-11-22 0:34 ` Michael Ellerman
-- strict thread matches above, loose matches on Subject: below --
2016-10-30 21:34 [PATCH] " Christophe JAILLET
2016-10-31 6:27 ` Andrew Donnellan
2016-10-31 9:50 ` Michael Ellerman
2016-11-16 1:54 ` Ian Munsie
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=87eg2unnil.fsf@concordia.ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=christophe.jaillet@wanadoo.fr \
--cc=fbarrat@linux.vnet.ibm.com \
--cc=imunsie@au1.ibm.com \
--cc=jim.epost@gmail.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.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).