From: kbuild test robot <fengguang.wu@intel.com>
To: Alex Smith <alex.smith@imgtec.com>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
Ralf Baechle <ralf@linux-mips.org>,
Markos Chandras <markos.chandras@imgtec.com>
Subject: awk: scripts/ld-version.sh: line 4: regular expression compile failed (missing '(')
Date: Sun, 29 Nov 2015 06:45:09 +0800 [thread overview]
Message-ID: <201511290608.3xJGoZYZ%fengguang.wu@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1107 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 8003a573560ae96540bce2a698347c6d502e2997
commit: ebb5e78cc63417a35254a791de66e1cc84f963cc MIPS: Initial implementation of a VDSO
date: 3 weeks ago
config: mips-allnoconfig (attached as .config)
reproduce:
wget https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
git checkout ebb5e78cc63417a35254a791de66e1cc84f963cc
# save the attached .config to linux build tree
make.cross ARCH=mips
All errors (new ones prefixed by >>):
>> awk: scripts/ld-version.sh: line 4: regular expression compile failed (missing '(')
.*)
--
>> awk: scripts/ld-version.sh: line 4: regular expression compile failed (missing '(')
.*)
/bin/sh: line 0: [: -gt: unary operator expected
arch/mips/vdso/Makefile:30: MIPS VDSO requires binutils > 2.24
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/octet-stream, Size: 5084 bytes --]
next reply other threads:[~2015-11-28 22:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-28 22:45 kbuild test robot [this message]
2015-12-05 23:17 kbuild test robot
2015-12-12 23:01 kbuild test robot
2016-01-10 0:51 kbuild test robot
2016-02-27 23:48 kbuild test robot
2016-03-05 23:36 kbuild 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=201511290608.3xJGoZYZ%fengguang.wu@intel.com \
--to=fengguang.wu@intel.com \
--cc=alex.smith@imgtec.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=markos.chandras@imgtec.com \
--cc=ralf@linux-mips.org \
/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®