From: Guenter Roeck <linux@roeck-us.net>
To: kbuild test robot <fengguang.wu@intel.com>
Cc: kbuild-all@01.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Ralf Baechle <ralf@linux-mips.org>,
Fengguang Wu <fengguang.wu@intel.com>
Subject: Re: arch/mips/vdso/gettimeofday.c:1:0: error: '-march=r3900' requires '-mfp32'
Date: Tue, 5 Jan 2016 00:09:14 -0800 [thread overview]
Message-ID: <568B7A2A.1000608@roeck-us.net> (raw)
In-Reply-To: <201601051556.2YMiXcw0%fengguang.wu@intel.com>
On 01/04/2016 11:23 PM, kbuild test robot wrote:
> Hi Guenter,
>
> First bad commit (maybe != root cause):
>
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> head: 168309855a7d1e16db751e9c647119fe2d2dc878
> commit: 398c7500a1f5f74e207bd2edca1b1721b3cc1f1e MIPS: VDSO: Fix build error with binutils 2.24 and earlier
> date: 6 days ago
> config: mips-jmr3927_defconfig (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 398c7500a1f5f74e207bd2edca1b1721b3cc1f1e
> # save the attached .config to linux build tree
> make.cross ARCH=mips
>
> All errors (new ones prefixed by >>):
>
>>> arch/mips/vdso/gettimeofday.c:1:0: error: '-march=r3900' requires '-mfp32'
> /*
> ^
>
AFAICS this is using the mips cross compiler version 4.9.0 from kernel.org [1],
which in turn uses binutils 2.24. At least this is what make.cross tries to install.
I downloaded it and used it to compile both the attached configuration as well
as jmr3927_defconfig. Both are building just fine for me. On top of that,
arch/mips/vdso/gettimeofday.c should not build in the first place with binutils 2.24
(and doesn't build for me).
What am I missing ?
Guenter
---
[1] https://www.kernel.org/pub/tools/crosstool/files/bin/x86_64/4.9.0/x86_64-gcc-4.9.0-nolibc_mips-linux.tar.xz
next prev parent reply other threads:[~2016-01-05 8:09 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-05 7:23 arch/mips/vdso/gettimeofday.c:1:0: error: '-march=r3900' requires '-mfp32' kbuild test robot
2016-01-05 8:09 ` Guenter Roeck [this message]
2016-01-05 8:22 ` Fengguang Wu
2016-01-05 14:02 ` Guenter Roeck
2016-01-05 14:30 ` Fengguang Wu
2016-01-05 15:15 ` Guenter Roeck
2016-01-06 11:50 ` Fengguang Wu
2016-01-06 11:59 ` Fengguang Wu
2016-01-06 12:09 ` [kbuild-all] " Fengguang Wu
2016-01-05 14:35 ` Ralf Baechle
-- strict thread matches above, loose matches on Subject: below --
2016-02-28 8:42 kbuild test robot
2016-02-28 10:09 ` Guenter Roeck
2016-03-06 6:56 kbuild test robot
2016-03-13 9:16 kbuild test robot
2016-03-20 1:56 kbuild test robot
2016-04-03 9:23 kbuild test robot
2016-04-17 6:32 kbuild test robot
2016-07-22 17:28 kbuild test robot
2016-08-01 20:24 kbuild test robot
2016-08-28 11:23 kbuild test robot
2016-09-03 23:54 kbuild test robot
2016-09-14 16:02 kbuild test robot
2016-09-23 2:24 kbuild test robot
2016-10-02 2:39 kbuild test robot
2016-10-16 2:49 kbuild test robot
2016-11-05 23:48 kbuild test robot
2016-11-13 2:01 kbuild test robot
2016-12-11 1:21 kbuild test robot
2017-01-01 17:19 kbuild test robot
2017-01-15 1:51 kbuild test robot
2017-02-05 15:49 kbuild test robot
2017-02-12 0:17 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=568B7A2A.1000608@roeck-us.net \
--to=linux@roeck-us.net \
--cc=fengguang.wu@intel.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--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 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.