From: Miguel Ojeda <ojeda@kernel.org>
To: naresh.kamboju@linaro.org
Cc: 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,
nathan@kernel.org, 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:48:45 +0200 [thread overview]
Message-ID: <20250430154845.795993-1-ojeda@kernel.org> (raw)
In-Reply-To: <CA+G9fYtN2ie+YtK3H9mrQ5QqrSCFGGjVbtJcfiYX0oHMVWMn9w@mail.gmail.com>
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.
Thanks!
Cheers,
Miguel
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
WARNING: multiple messages have this Message-ID (diff)
From: Miguel Ojeda <ojeda@kernel.org>
To: naresh.kamboju@linaro.org
Cc: 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,
nathan@kernel.org, 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:48:45 +0200 [thread overview]
Message-ID: <20250430154845.795993-1-ojeda@kernel.org> (raw)
In-Reply-To: <CA+G9fYtN2ie+YtK3H9mrQ5QqrSCFGGjVbtJcfiYX0oHMVWMn9w@mail.gmail.com>
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.
Thanks!
Cheers,
Miguel
next prev parent reply other threads:[~2025-04-30 16:04 UTC|newest]
Thread overview: 8+ 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-23 14:45 ` Naresh Kamboju
2025-04-30 15:48 ` Miguel Ojeda [this message]
2025-04-30 15:48 ` Miguel Ojeda
2025-05-01 0:44 ` Nathan Chancellor
2025-05-01 0:44 ` Nathan Chancellor
2025-05-01 9:12 ` Alexandre Ghiti
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=20250430154845.795993-1-ojeda@kernel.org \
--to=ojeda@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=nathan@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.