mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Nathan Chancellor <nathan@kernel.org>
To: Philip Li <philip.li@intel.com>
Cc: kernel test robot <lkp@intel.com>,
	Peter Foley <pefoley2@pefoley.com>,
	llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
	linux-kernel@vger.kernel.org, Richard Weinberger <richard@nod.at>
Subject: Re: /usr/bin/ld: ../lib/LLVMgold.so: cannot open shared object file: No such file or directory
Date: Fri, 16 Aug 2024 13:44:38 -0700	[thread overview]
Message-ID: <20240816204438.GA3870443@thelio-3990X> (raw)
In-Reply-To: <Zr68AOqR2A3hKv2k@rli9-mobl>

On Fri, Aug 16, 2024 at 10:40:00AM +0800, Philip Li wrote:
> On Fri, Aug 16, 2024 at 09:08:02AM +0800, kernel test robot wrote:
> > tree:   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> > head:   d7a5aa4b3c007fae50405ca75c40258d90300e96
> > commit: 83e913f52aba69149261742aa9ea4ceea7bf182d um: Support LTO
> > date:   1 year, 6 months ago
> > config: um-randconfig-001-20240815 (https://download.01.org/0day-ci/archive/20240816/202408160932.BvHwO6Qo-lkp@intel.com/config)
> > compiler: clang version 16.0.6 (https://github.com/llvm/llvm-project 7cbf1a2591520c2491aa35339f227775f4d3adf6)
> > reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240816/202408160932.BvHwO6Qo-lkp@intel.com/reproduce)
> > 
> > If you fix the issue in a separate patch/commit (i.e. not just a new version of
> > the same patch/commit), kindly add following tags
> > | Reported-by: kernel test robot <lkp@intel.com>
> > | Closes: https://lore.kernel.org/oe-kbuild-all/202408160932.BvHwO6Qo-lkp@intel.com/
> > 
> > All errors (new ones prefixed by >>):
> 
> kindly ignore this false report, which should be test environment issue. We will
> follow up to fix this.

For what it's worth, this is somewhat our bug, as ARCH=um uses $(CC) to
link, which means that ld.lld is not getting used for the final link in
the vast majority of cases (because clang defaults to just 'ld' for
Linux). This is problematic in the case of LTO because the compiler
generates LLVM bitcode that GNU ld does not understand so it needs the
LLVMgold plugin. That shouldn't be necessary but ld.lld does not worth
with ARCH=um for tangential reasons:

https://github.com/ClangBuiltLinux/linux/issues/1715

> > 
> > >> /usr/bin/ld: ../lib/LLVMgold.so: cannot open shared object file: No such file or directory
> >    clang-16: error: linker command failed with exit code 1 (use -v to see invocation)
> > --
> > >> llvm-objcopy: error: 'arch/x86/um/vdso/vdso.so.dbg': No such file or directory
> > 
> > -- 
> > 0-DAY CI Kernel Test Service
> > https://github.com/intel/lkp-tests/wiki
> > 
> 

      reply	other threads:[~2024-08-16 20:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-16  1:08 kernel test robot
2024-08-16  2:40 ` Philip Li
2024-08-16 20:44   ` Nathan Chancellor [this message]

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=20240816204438.GA3870443@thelio-3990X \
    --to=nathan@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=llvm@lists.linux.dev \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=pefoley2@pefoley.com \
    --cc=philip.li@intel.com \
    --cc=richard@nod.at \
    /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

all inboxes | Powered by JetHome®