linux-kernel - Re: /usr/bin/ld: ../lib/LLVMgold.so: cannot open shared object file: No such file or directory

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20240816204438.GA3870443@thelio-3990X>
Date: Fri, 16 Aug 2024 13:44:38 -0700
From: Nathan Chancellor <nathan@...nel.org>
To: Philip Li <philip.li@...el.com>
Cc: kernel test robot <lkp@...el.com>, Peter Foley <pefoley2@...oley.com>,
	llvm@...ts.linux.dev, oe-kbuild-all@...ts.linux.dev,
	linux-kernel@...r.kernel.org, Richard Weinberger <richard@....at>
Subject: Re: /usr/bin/ld: ../lib/LLVMgold.so: cannot open shared object file:
 No such file or directory

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@...el.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
> > 
>