From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com
Subject: [mszeredi-fuse:for-next 26/52] /usr/lib/gcc-cross/aarch64-linux-gnu/14/../../../../aarch64-linux-gnu/bin/ld: cannot find -lfuse3: No such file or directory
Date: Sun, 18 Oct 2026 09:43:40 +0200 [thread overview]
Message-ID: <202610170140.tU9LUfij-lkp@intel.com> (raw)
::::::
:::::: Manual check reason: "low confidence bisect report"
::::::
BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
CC: fuse-devel@lists.sourceforge.net
TO: Luis Henriques <luis@igalia.com>
CC: Miklos Szeredi <mszeredi@redhat.com>
CC: Amir Goldstein <amir73il@gmail.com>
tree: https://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/fuse.git for-next
head: 4dd8d396740168f5379f332ad2c165d7f0f91953
commit: c7d054ac8ee905801db370b3fddbf2bd0775ca5d [26/52] selftests/fuse: factor-out test fixture setup/teardown
:::::: branch date: 8 hours ago
:::::: commit date: 35 hours ago
config: arm64-allnoconfig-bpf (https://download.01.org/0day-ci/archive/20261017/202610170140.tU9LUfij-lkp@intel.com/config)
compiler: aarch64-linux-gnu-gcc (Debian 14.2.0-19) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20261017/202610170140.tU9LUfij-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/r/202610170140.tU9LUfij-lkp@intel.com/
Note: the mszeredi-fuse/for-next HEAD 4dd8d396740168f5379f332ad2c165d7f0f91953 builds fine.
It only hurts bisectability.
All errors (new ones prefixed by >>):
>> /usr/lib/gcc-cross/aarch64-linux-gnu/14/../../../../aarch64-linux-gnu/bin/ld: cannot find -lfuse3: No such file or directory
collect2: error: ld returned 1 exit status
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-10-18 7:52 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202610170140.tU9LUfij-lkp@intel.com \
--to=lkp@intel.com \
--cc=oe-kbuild@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.