From: Helge Deller <deller@gmx.de>
To: Meelis Roos <mroos@linux.ee>
Cc: linux-parisc@vger.kernel.org
Subject: Re: INEQUIVALENT ALIASES in 3.11-rc3
Date: Wed, 31 Jul 2013 11:44:27 +0200 [thread overview]
Message-ID: <51F8DC7B.9090504@gmx.de> (raw)
In-Reply-To: <alpine.SOC.1.00.1307310003070.19136@math.ut.ee>
On 07/30/2013 11:06 PM, Meelis Roos wrote:
> I tried 3.11-rc3 yesterday on my RP3440. It works, but has acquired a
> new warning during Gentoo emerge cycle:
> [ 922.492000] INEQUIVALENT ALIASES 0x4197a000 and 0x7b000 in file conftest
> [ 922.492000] INEQUIVALENT ALIASES 0x4197a000 and 0x7b000 in file conftest
> [ 922.492000] INEQUIVALENT ALIASES 0x4197a000 and 0x7b000 in file conftest
> [ 922.492000] INEQUIVALENT ALIASES 0x4197a000 and 0x7b000 in file conftest
> [ 922.492000] INEQUIVALENT ALIASES 0x4197a000 and 0x7b000 in file conftest
> [ 4577.536000] INEQUIVALENT ALIASES 0x41a76000 and 0x7b000 in file conftest
> [ 4577.536000] INEQUIVALENT ALIASES 0x41a76000 and 0x7b000 in file conftest
> [ 4577.536000] INEQUIVALENT ALIASES 0x41a76000 and 0x7b000 in file conftest
> [ 4577.536000] INEQUIVALENT ALIASES 0x41a76000 and 0x7b000 in file conftest
> [ 4577.536000] INEQUIVALENT ALIASES 0x41a76000 and 0x7b000 in file conftest
>
> There is no file named conftest present after emerge, so it must have
> been some temporary program.
Those warnings are uncritical - but you should update binutils.
See: http://permalink.gmane.org/gmane.linux.ports.parisc/3834
Helge
next prev parent reply other threads:[~2013-07-31 9:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-30 21:06 INEQUIVALENT ALIASES in 3.11-rc3 Meelis Roos
2013-07-30 22:21 ` Matt Turner
2013-07-31 9:44 ` Helge Deller [this message]
2013-07-31 14:40 ` John David Anglin
2013-08-01 9:28 ` Meelis Roos
2013-08-01 14:15 ` John David Anglin
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=51F8DC7B.9090504@gmx.de \
--to=deller@gmx.de \
--cc=linux-parisc@vger.kernel.org \
--cc=mroos@linux.ee \
/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