From: kernel test robot <lkp@intel.com>
To: Johannes Berg <johannes.berg@intel.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: [linux-next:master 8923/12096] /usr/lib/gcc/i686-linux-gnu/14/../../../../i686-linux-gnu/bin/ld:./arch/um/kernel/vmlinux.lds:167: syntax error
Date: Wed, 30 Sep 2026 06:12:28 +0200 [thread overview]
Message-ID: <202609300549.Vy4VMT1M-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 6474fa070f2b8013b4b87350b775b8c3be6e8aac
commit: 779c65ede6800595ec620b0b10aae7d5a5469cbd [8923/12096] um: link .lbss/.ldata/.lrodata correctly
config: um-randconfig-2000-20260930 (https://download.01.org/0day-ci/archive/20260930/202609300549.Vy4VMT1M-lkp@intel.com/config)
compiler: clang version 24.0.0git (https://github.com/llvm/llvm-project 7615da10b75c57286a4032eac8bb43c1b8d2ba46)
rustc: rustc 1.96.0 (ac68faa20 2026-05-25)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260930/202609300549.Vy4VMT1M-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/202609300549.Vy4VMT1M-lkp@intel.com/
All errors (new ones prefixed by >>):
/usr/lib/gcc/i686-linux-gnu/14/../../../../i686-linux-gnu/bin/ld:./arch/um/kernel/vmlinux.lds:167: ignoring invalid character `*' in script
>> /usr/lib/gcc/i686-linux-gnu/14/../../../../i686-linux-gnu/bin/ld:./arch/um/kernel/vmlinux.lds:167: syntax error
clang: error: linker command failed with exit code 1 (use -v to see invocation)
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-09-30 4:13 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=202609300549.Vy4VMT1M-lkp@intel.com \
--to=lkp@intel.com \
--cc=johannes.berg@intel.com \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@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.