From: Markos Chandras <Markos.Chandras@imgtec.com>
To: Joshua Kinard <kumba@gentoo.org>,
Linux MIPS List <linux-mips@linux-mips.org>,
Matthew Fortune <Matthew.Fortune@imgtec.com>
Subject: Re: IP28: "Inconsistent ISA" messages during kernel build
Date: Tue, 12 May 2015 09:23:48 +0100 [thread overview]
Message-ID: <5551B894.9000204@imgtec.com> (raw)
In-Reply-To: <55516EF3.7010706@gentoo.org>
On 05/12/2015 04:09 AM, Joshua Kinard wrote:
>
> Has anyone tried to build an IP28 kernel lately? I've been getting quite a few
> warnings out of the linker regarding e_flags and the new .MIPS.abiflags stuff.
> Not seen it on the other SGI platforms, so I am assuming this has something to
> do with what flags are passed to the compiler/linker.
>
> mips64-unknown-linux-gnu-ld: fs/ext4/symlink.o: warning: Inconsistent ISA
> between e_flags and .MIPS.abiflags
> mips64-unknown-linux-gnu-ld: fs/ext4/symlink.o: warning: Inconsistent ISA
> extensions between e_flags and .MIPS.abiflags
>
> Seeing this on a build of 4.0.2 based off of a 20150418 checkout from git.
>
> --J
>
Hi,
I presume you are using binutils >= 2.25? I have seen this problem in my
local build tests as well and I discussed this with Matthew (now on CC).
It seems it's an 'innocent' warning added to binutils 2.25 but I am not
sure if this is now fixed or not. Matthew might be able to provide more
information.
--
markos
next prev parent reply other threads:[~2015-05-12 8:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-12 3:09 IP28: "Inconsistent ISA" messages during kernel build Joshua Kinard
2015-05-12 8:23 ` Markos Chandras [this message]
2015-05-12 9:00 ` Matthew Fortune
2015-05-12 16:22 ` Joshua Kinard
2015-05-12 16:59 ` Aaro Koskinen
2015-05-12 19:06 ` Matthew Fortune
2015-05-12 16:26 ` Joshua Kinard
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=5551B894.9000204@imgtec.com \
--to=markos.chandras@imgtec.com \
--cc=Matthew.Fortune@imgtec.com \
--cc=kumba@gentoo.org \
--cc=linux-mips@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.