Building the Linux kernel with Clang and LLVM
 help / color / mirror / Atom feed
From: Nathan Chancellor <nathan@kernel.org>
To: Miguel Ojeda <ojeda@kernel.org>
Cc: naresh.kamboju@linaro.org, anders.roxell@linaro.org,
	aou@eecs.berkeley.edu, arnd@arndb.de, dan.carpenter@linaro.org,
	linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org,
	lkft-triage@lists.linaro.org, llvm@lists.linux.dev,
	masahiroy@kernel.org, namcao@linutronix.de, palmer@dabbelt.com,
	regressions@lists.linux.dev
Subject: Re: next-20250422: arch/riscv/kernel/vdso/vdso.so.dbg: dynamic relocations are not supported
Date: Wed, 30 Apr 2025 17:44:34 -0700	[thread overview]
Message-ID: <20250501004434.GA3762678@ax162> (raw)
In-Reply-To: <20250430154845.795993-1-ojeda@kernel.org>

On Wed, Apr 30, 2025 at 05:48:45PM +0200, Miguel Ojeda wrote:
> On Wed, 23 Apr 2025 20:15:45 +0530 Naresh Kamboju <naresh.kamboju@linaro.org> wrote:
> >
> > build errors with clang
> > ld.lld: error: version script assignment of 'LINUX_4.15' to symbol
> > '__vdso_getrandom' failed: symbol not defined
> > llvm-nm: error: arch/riscv/kernel/compat_vdso/compat_vdso.so.dbg: No
> > such file or directory
> 
> I have also been seeing this too in my Rust-enabled builds for a few
> days at least.

I forgot to follow up here and say that I sent a patch for this, it just
needs to be applied by the RISC-V folks.

https://lore.kernel.org/20250423-riscv-fix-compat_vdso-lld-v2-1-b7bbbc244501@kernel.org/

Cheers,
Nathan

  reply	other threads:[~2025-05-01  0:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-23 14:45 next-20250422: arch/riscv/kernel/vdso/vdso.so.dbg: dynamic relocations are not supported Naresh Kamboju
2025-04-30 15:48 ` Miguel Ojeda
2025-05-01  0:44   ` Nathan Chancellor [this message]
2025-05-01  9:12     ` Alexandre Ghiti

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=20250501004434.GA3762678@ax162 \
    --to=nathan@kernel.org \
    --cc=anders.roxell@linaro.org \
    --cc=aou@eecs.berkeley.edu \
    --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=masahiroy@kernel.org \
    --cc=namcao@linutronix.de \
    --cc=naresh.kamboju@linaro.org \
    --cc=ojeda@kernel.org \
    --cc=palmer@dabbelt.com \
    --cc=regressions@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