All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com
Subject: [thomas-weissschuh:b4/vdso-ptp 25/34] ld: cannot find loongarch64-linux-gcc:: No such file or directory
Date: Thu, 5 Jun 2025 00:26:56 +0800	[thread overview]
Message-ID: <202506050031.XC2lJsg1-lkp@intel.com> (raw)

:::::: 
:::::: Manual check reason: "only suspicious fbc files changed"
:::::: 

BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
TO: "Thomas Weißschuh" <thomas.weissschuh@linutronix.de>

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/thomas.weissschuh/linux.git b4/vdso-ptp
head:   07453cfef5683be5805a70316b1345e7fbeb716b
commit: e844e7134d3f49799bf7a762d2870dfc9b228bfa [25/34] libgcc
:::::: branch date: 7 hours ago
:::::: commit date: 7 hours ago
config: loongarch-randconfig-002-20250604 (https://download.01.org/0day-ci/archive/20250605/202506050031.XC2lJsg1-lkp@intel.com/config)
compiler: loongarch64-linux-gcc (GCC) 15.1.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250605/202506050031.XC2lJsg1-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/202506050031.XC2lJsg1-lkp@intel.com/

All errors (new ones prefixed by >>):

>> ld: cannot find loongarch64-linux-gcc:: No such file or directory
>> ld: cannot find note:: No such file or directory
>> ld: cannot find ABI: No such file or directory
>> ld: cannot find lp64s: No such file or directory
>> ld: cannot find is: No such file or directory
>> ld: cannot find not: No such file or directory
>> ld: cannot find enabled: No such file or directory
>> ld: cannot find at: No such file or directory
>> ld: cannot find configure-time,: No such file or directory
>> ld: cannot find the: No such file or directory
>> ld: cannot find linker: No such file or directory
>> ld: cannot find might: No such file or directory
>> ld: cannot find report: No such file or directory
>> ld: cannot find an: No such file or directory
>> ld: cannot find error: No such file or directory
>> ld: cannot find loongarch64-linux-gcc:: No such file or directory
>> ld: cannot find note:: No such file or directory
>> ld: cannot find ABI: No such file or directory
>> ld: cannot find with: No such file or directory
>> ld: cannot find startfiles:: No such file or directory
   ld: cannot find lp64d: 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:[~2025-06-04 16:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-04 16:26 kernel test robot [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-06-18  2:50 [thomas-weissschuh:b4/vdso-ptp 25/34] ld: cannot find loongarch64-linux-gcc:: No such file or directory kernel test robot

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=202506050031.XC2lJsg1-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.