From: Naresh Kamboju <naresh.kamboju@linaro.org>
To: open list <linux-kernel@vger.kernel.org>,
clang-built-linux <llvm@lists.linux.dev>,
lkft-triage@lists.linaro.org,
linux-riscv <linux-riscv@lists.infradead.org>
Cc: "Mike Rapoport" <rppt@kernel.org>,
"Phil Mathieu-Daudé" <philmd@linaro.org>,
"Luis Chamberlain" <mcgrof@kernel.org>,
"Arnd Bergmann" <arnd@arndb.de>,
"Dan Carpenter" <dan.carpenter@linaro.org>,
"Anders Roxell" <anders.roxell@linaro.org>
Subject: riscv32: mm/init.c:1495:11: error: use of undeclared identifier 'MODULES_VADDR'
Date: Fri, 26 Apr 2024 21:08:51 +0530 [thread overview]
Message-ID: <CA+G9fYvy+3XKDu+U-V3dXLsUPm1ybR_vn5djNvxXnXr85U9UhQ@mail.gmail.com> (raw)
The Linux next today's tag next-20240426 riscv32 builds failed due to following
build warnings / errors.
riscv32:
- rv32-clang-18-defconfig
- rv32-clang-18-allnoconfig
- rv32-clang-18-tinyconfig
Build log:
----
arch/riscv/mm/init.c:1495:11: error: use of undeclared identifier
'MODULES_VADDR'
1495 | start = MODULES_VADDR;
| ^
arch/riscv/mm/init.c:1496:9: error: use of undeclared identifier 'MODULES_END'
1496 | end = MODULES_END;
| ^
2 errors generated.
metadata:
git_repo: https://gitlab.com/Linaro/lkft/mirrors/next/linux-next
git_sha: bb7a2467e6beef44a80a17d45ebf2931e7631083
git_short_log: bb7a2467e6be ("Add linux-next specific files for 20240426")
git_describe: next-20240426
steps to reproduce:
# tuxmake --runtime podman --target-arch riscv --toolchain clang-18
--kconfig defconfig --kconfig-add rv32_defconfig LLVM=1
Links:
- https://storage.tuxsuite.com/public/linaro/lkft/builds/2fdCURo2mABucb6hDzrLnPoTWMx/
- https://qa-reports.linaro.org/lkft/linux-next-master/build/next-20240426/testrun/23674184/suite/build/test/rv32-clang-18-defconfig/details/
--
Linaro LKFT
https://lkft.linaro.org
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
reply other threads:[~2024-04-26 15:39 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CA+G9fYvy+3XKDu+U-V3dXLsUPm1ybR_vn5djNvxXnXr85U9UhQ@mail.gmail.com \
--to=naresh.kamboju@linaro.org \
--cc=anders.roxell@linaro.org \
--cc=arnd@arndb.de \
--cc=dan.carpenter@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=lkft-triage@lists.linaro.org \
--cc=llvm@lists.linux.dev \
--cc=mcgrof@kernel.org \
--cc=philmd@linaro.org \
--cc=rppt@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 read-only IMAP folder(s) and NNTP newsgroup(s).