From: Jon Hunter <jonathanh@nvidia.com>
To: Miles Chen <miles.chen@mediatek.com>,
Stefan Wahren <stefan.wahren@i2se.com>,
Jisheng Zhang <jszhang@kernel.org>,
open list <linux-kernel@vger.kernel.org>,
Palmer Dabbelt <palmerdabbelt@google.com>
Cc: "linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>
Subject: Re: Build error: ‘EM_RISCV’ undeclared
Date: Fri, 24 Sep 2021 10:30:30 +0100 [thread overview]
Message-ID: <cf7eea1d-a628-c6c4-270f-fa9895192b24@nvidia.com> (raw)
In-Reply-To: <78cf3af71e035a79d021d17c6fd8a09dd1e4984d.camel@mediatek.com>
On 13/09/2021 03:49, Miles Chen wrote:
> On Sun, 2021-09-12 at 12:29 +0200, Stefan Wahren wrote:
>> Hi,
>>
>> i tried to compile current torvalds tree
>> ("78e709522d2c012cb0daad2e668506637bffb7c2") for
>> arm/multi_v7_defconfig
>> and get the following build issue:
>>
>> UPD include/generated/utsrelease.h
>> scripts/sorttable.c: In function ‘do_file’:
>> scripts/sorttable.c:352:7: error: ‘EM_RISCV’ undeclared (first use in
>> this function)
>> case EM_RISCV:
>> ^
>> scripts/sorttable.c:352:7: note: each undeclared identifier is
>> reported
>> only once for each function it appears in
>>
>> I assume this is caused by:
>>
>> 54fed35fd3939398be292e4090b0b1c5ff2238b4 ("riscv: Enable
>> BUILDTIME_TABLE_SORT")
>
> I hit this error too. I add the follow conditional EM_RISCV
> definition in sorttable.c to build pass (arm64/defconfig).
>
> I will submit a patch out.
>
> diff --git a/scripts/sorttable.c b/scripts/sorttable.c
> index f355869c65cd..6ee4fa882919 100644
> --- a/scripts/sorttable.c
> +++ b/scripts/sorttable.c
> @@ -54,6 +54,10 @@
> #define EM_ARCV2 195
> #endif
>
> +#ifndef EM_RISCV
> +#define EM_RISCV 243
> +#endif
> +
This is still broken in the mainline. Any plans to get this fix merged
there? I believe it has now been broken for nearly 2 weeks.
Thanks!
Jon
--
nvpublic
next prev parent reply other threads:[~2021-09-24 9:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-12 10:29 Build error: ‘EM_RISCV’ undeclared Stefan Wahren
2021-09-13 2:49 ` Miles Chen
2021-09-24 9:30 ` Jon Hunter [this message]
2021-09-24 12:55 ` Jon Hunter
2021-09-24 18:05 ` Stefan Wahren
2021-09-24 19:01 ` Jon Hunter
2021-09-24 19:42 ` 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=cf7eea1d-a628-c6c4-270f-fa9895192b24@nvidia.com \
--to=jonathanh@nvidia.com \
--cc=jszhang@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=miles.chen@mediatek.com \
--cc=palmerdabbelt@google.com \
--cc=stefan.wahren@i2se.com \
/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).