From: Meelis Roos <mroos@linux.ee>
To: Masahiro Yamada <masahiroy@kernel.org>, Helge Deller <deller@gmx.de>
Cc: Parisc List <linux-parisc@vger.kernel.org>,
Linux Kernel Development <linux-kernel@vger.kernel.org>
Subject: Re: linux-parisc compile failure in current git
Date: Thu, 10 Jun 2021 18:13:51 +0300 [thread overview]
Message-ID: <946c5f64-5cca-2395-5e69-6e573ea6a72b@linux.ee> (raw)
In-Reply-To: <CAK7LNATuzry1MUj-VruOVUwU_nH2xJd_2SxD_s_Z1QBb3PVnQw@mail.gmail.com>
10.06.21 05:03 Masahiro Yamada wrote:
> There are some options
>
> [option 1]
> revert the parisc bit of 23243c1ace9fb4eae2f75e0fe0ece8e3219fb4f3
> This will restore the functionality you may want, but
> as I said above, Kconfig is doing pointless things.
>
> [option 2]
> Stop using cc-cross-prefix, and pass CROSS_COMPILE explicitly.
> This is what many architectures including arm, arm64 do.
> You need to explicitly pass CROSS_COMPILE=aarch64-linux-gnu- etc.
> if you are cross-compiling arm64.
>
> [option 3]
> Introduce ARCH=parisc64.
>
> When you are building 64-bit kernel, you can pass ARCH=parisc64
>
> A patch attached. (but not tested much)
Tested on my gentoo with separate compilers. Compiles fine, boots and has so far compiled 21 paxkageswith no trouble so seems to work - thank you!
--
Meelis Roos <mroos@linux.ee>
prev parent reply other threads:[~2021-06-10 15:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <892b6ab7-862c-1c0a-2996-0f8408e5043d@linux.ee>
2021-06-09 22:49 ` linux-parisc compile failure in current git Helge Deller
2021-06-10 2:03 ` Masahiro Yamada
2021-06-10 7:03 ` Helge Deller
2021-06-17 1:47 ` Masahiro Yamada
2021-06-23 20:33 ` Helge Deller
2022-08-17 20:59 ` Randy Dunlap
2022-08-19 10:38 ` Helge Deller
2022-08-19 12:45 ` Masahiro Yamada
2022-08-19 13:54 ` Helge Deller
2022-08-19 16:41 ` Masahiro Yamada
2022-08-19 17:58 ` Helge Deller
2022-08-20 1:22 ` Randy Dunlap
2022-08-20 1:17 ` Randy Dunlap
2021-06-10 15:13 ` Meelis Roos [this message]
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=946c5f64-5cca-2395-5e69-6e573ea6a72b@linux.ee \
--to=mroos@linux.ee \
--cc=deller@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-parisc@vger.kernel.org \
--cc=masahiroy@kernel.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).