Linux PARISC architecture development
 help / color / mirror / Atom feed
From: John David Anglin <dave.anglin@bell.net>
To: Chen Gang <gang.chen@asianux.com>
Cc: James Bottomley <James.Bottomley@HansenPartnership.com>,
	Helge Deller <deller@gmx.de>,
	Parisc List <linux-parisc@vger.kernel.org>
Subject: Re: [Suggestion] parisc: kernel: about section mismatch warning.
Date: Mon, 29 Jul 2013 09:47:32 -0400	[thread overview]
Message-ID: <BLU0-SMTP611AEF17EB77D8F3C171E397550@phx.gbl> (raw)
In-Reply-To: <51F62C8E.6080003@asianux.com>

On 29-Jul-13, at 4:49 AM, Chen Gang wrote:

> After use own built cross compiler (gcc-4.9.0, binutils-2.23.2 with
> 'hppa64-gchen-linux'), no the related warnings any more.
>
> The original compiler which I used ('hppa64-linux-gnu') is incorrect.

I haven't seen the warning with any recent compiler and possibly your  
compiler
selection versus CONFIG_64BIT was wrong.  What does 'hppa64-linux-gnu - 
v'
show?

gcc-4.9.0 is not released and any particular snapshot may be buggy.   
Suggest using
4.8 branch.

Dave
--
John David Anglin	dave.anglin@bell.net




  reply	other threads:[~2013-07-29 13:47 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-24  8:12 [PATCH] parisc: Kconfig: use 'PA8X00' as the default choise instead of 'PA7000' Chen Gang
2013-07-24  8:27 ` [Suggestion] parisc: kernel: about section mismatch warning Chen Gang
2013-07-24 14:11   ` James Bottomley
2013-07-24 23:58     ` Chen Gang F T
2013-07-29  8:49       ` Chen Gang
2013-07-29 13:47         ` John David Anglin [this message]
2013-07-29 18:23           ` Helge Deller
2013-07-30  0:48           ` Chen Gang
2013-07-24 14:00 ` [PATCH] parisc: Kconfig: use 'PA8X00' as the default choise instead of 'PA7000' James Bottomley
2013-07-25  0:37   ` Chen Gang F T
2013-07-26 20:08     ` Helge Deller
2013-07-29  1:11       ` Chen Gang
2013-07-29  8:39         ` [Suggestion] parisc: about the warnings "unsigned expression < 0 is always false" Chen Gang

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=BLU0-SMTP611AEF17EB77D8F3C171E397550@phx.gbl \
    --to=dave.anglin@bell.net \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=deller@gmx.de \
    --cc=gang.chen@asianux.com \
    --cc=linux-parisc@vger.kernel.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