From: kbuild test robot <fengguang.wu@intel.com>
To: James Hogan <james.hogan@imgtec.com>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
Ralf Baechle <ralf@linux-mips.org>,
"Maciej W. Rozycki" <macro@imgtec.com>
Subject: cc1: error: '-march=r3900' requires '-mfp32'
Date: Sun, 23 Oct 2016 13:24:32 +0800 [thread overview]
Message-ID: <201610231331.RSfWSd5J%fengguang.wu@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 961 bytes --]
Hi James,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 0c2b6dc4fd4fa13796b319aae969a009f03222c6
commit: 034827c727f7f3946a18355b63995b402c226c82 MIPS: Fix -mabi=64 build of vdso.lds
date: 12 days ago
config: mips-jmr3927_defconfig (attached as .config)
compiler: mips-linux-gnu-gcc (Debian 6.1.1-9) 6.1.1 20160705
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 034827c727f7f3946a18355b63995b402c226c82
# save the attached .config to linux build tree
make.cross ARCH=mips
All errors (new ones prefixed by >>):
>> cc1: error: '-march=r3900' requires '-mfp32'
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 10766 bytes --]
next reply other threads:[~2016-10-23 5:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-23 5:24 kbuild test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-02-12 1:43 cc1: error: '-march=r3900' requires '-mfp32' kbuild test robot
2017-02-05 17:01 kbuild test robot
2017-01-15 2:56 kbuild test robot
2017-01-01 17:46 kbuild test robot
2016-12-11 1:48 kbuild test robot
2016-12-04 4:12 kbuild test robot
2016-11-13 2:48 kbuild test robot
2016-11-06 0:24 kbuild test robot
2016-10-16 3:13 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=201610231331.RSfWSd5J%fengguang.wu@intel.com \
--to=fengguang.wu@intel.com \
--cc=james.hogan@imgtec.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=macro@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;
as well as URLs for NNTP newsgroup(s).