From: Jeff Johnson <quic_jjohnson@quicinc.com>
To: <linux-mips@vger.kernel.org>, <llvm@lists.linux.dev>
Subject: mips allmodconfig build error with llvm-18.1.7-x86_64
Date: Mon, 17 Jun 2024 08:50:00 -0700 [thread overview]
Message-ID: <a138bd58-80b3-4adb-8cbb-65e92a0d0b6e@quicinc.com> (raw)
As part of my tree-wide cleanup of missing MODULE_DESCRIPTION() macros I'm
trying to do allmodconfig builds for every architecture.
With:
export ARCH=mips
export LLVM=llvm-18.1.7-x86_64/bin/
make distclean
make allmodconfig
make -j$(nproc)
I'm getting build errors like:
Cannot find symbol for section 46: .text.free_initmem.
init/main.o: failed
Cannot find symbol for section 6: .text.copy_from_kernel_nofault_allowed.
mm/maccess.o: failed
Cannot find symbol for section 10: .text.arch_asym_cpu_priority.
kernel/sched/fair.o: failed
Interestingly, if I make 'defconfig' instead of 'allmodconfig' I don't see
this issue.
Any thoughts on how to have a successful mips allmodconfig build?
/jeff
next reply other threads:[~2024-06-17 15:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-17 15:50 Jeff Johnson [this message]
2024-06-17 17:44 ` mips allmodconfig build error with llvm-18.1.7-x86_64 Nathan Chancellor
2024-06-18 9:28 ` Maciej W. Rozycki
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=a138bd58-80b3-4adb-8cbb-65e92a0d0b6e@quicinc.com \
--to=quic_jjohnson@quicinc.com \
--cc=linux-mips@vger.kernel.org \
--cc=llvm@lists.linux.dev \
/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