From: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, Ralf Baechle <ralf@linux-mips.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
linux-mips@linux-mips.org
Subject: Re: linux-next: Tree for Jun 20
Date: Mon, 20 Jun 2016 22:59:20 +0100 [thread overview]
Message-ID: <57686738.70900@gmail.com> (raw)
In-Reply-To: <20160620160537.3ea30484@canb.auug.org.au>
On Monday 20 June 2016 07:05 AM, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20160617:
I just started trying gcc 6.1.0 for mips and mips allmodconfig is
failing with the error:
{standard input}: Assembler messages:
{standard input}:147: Error: number (0x9000000080000000) larger than 32 bits
{standard input}:176: Error: number (0x9000000080000000) larger than 32 bits
{standard input}:198: Error: number (0x9000000080000000) larger than 32 bits
make[3]: *** [arch/mips/mm/sc-ip22.o] Error 1
make[3]: *** Waiting for unfinished jobs....
make[2]: *** [arch/mips/mm] Error 2
make[2]: *** Waiting for unfinished jobs....
make[1]: *** [arch/mips] Error 2
make[1]: *** Waiting for unfinished jobs....
build log can be seen at:
https://travis-ci.org/sudipm-mukherjee/parport/jobs/138824794
regards
sudip
next prev parent reply other threads:[~2016-06-20 21:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-20 6:05 linux-next: Tree for Jun 20 Stephen Rothwell
2016-06-20 21:59 ` Sudip Mukherjee [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-06-20 5:26 Stephen Rothwell
2022-06-20 8:42 Stephen Rothwell
2019-06-20 10:46 Stephen Rothwell
2018-06-20 4:42 Stephen Rothwell
2017-06-20 6:00 Stephen Rothwell
2015-06-20 14:54 Stephen Rothwell
2014-06-20 5:36 Stephen Rothwell
2013-06-20 8:26 Stephen Rothwell
2012-06-20 7:35 Stephen Rothwell
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=57686738.70900@gmail.com \
--to=sudipm.mukherjee@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=linux-next@vger.kernel.org \
--cc=ralf@linux-mips.org \
--cc=sfr@canb.auug.org.au \
/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).