[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAJKOXPcfpTMr+KGLXCC2Kb5Hz+jSX+6KtCoPS-0qWdk2sazTeQ@mail.gmail.com>
Date: Fri, 31 Jan 2020 09:25:18 +0100
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Stafford Horne <shorne@...il.com>
Cc: Jonas Bonn <jonas@...thpole.se>,
Stefan Kristiansson <stefan.kristiansson@...nalahti.fi>,
Andrew Morton <akpm@...ux-foundation.org>,
openrisc@...ts.librecores.org,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
yamada.masahiro@...ionext.com
Subject: Re: [PATCH] openrisc: configs: Cleanup CONFIG_CROSS_COMPILE
On Thu, 30 Jan 2020 at 22:38, Stafford Horne <shorne@...il.com> wrote:
>
> +cc: Masahiro,
>
> On Thu, Jan 30, 2020 at 08:19:38PM +0100, Krzysztof Kozlowski wrote:
> > CONFIG_CROSS_COMPILE is gone since commit f1089c92da79 ("kbuild: remove
> > CONFIG_CROSS_COMPILE support").
>
> I see this patch is already in, but does it break 0-day test tools that depend
> on this CONFIG_CROSS_COMPILE setup? I guess its been in since 2018, so there
> should be no problem.
>
> Can you also help to update "Documentation/openrisc/openrisc_port.rst"? It
> mentions the build steps are:
>
> Build the Linux kernel as usual::
>
> make ARCH=openrisc defconfig
> make ARCH=openrisc
>
> This now changes, I used to use `make ARCH=openrisc CROSS_COMPILE=or1k-linux-`
> is this still going to work?
All cross compile platforms are being built like this, so I guess
openrisc should not be different. I will send a patch for the doc
update.
Best regards,
Krzysztof
Powered by blists - more mailing lists