SUPERH platform development
 help / color / mirror / Atom feed
From: Chen Gang <gang.chen@asianux.com>
To: linux-sh@vger.kernel.org
Subject: Re: [Suggestion] sh64: kernel: about the warning: "unexpected non-allocatable section".
Date: Tue, 30 Jul 2013 06:09:41 +0000	[thread overview]
Message-ID: <51F758A5.9010400@asianux.com> (raw)
In-Reply-To: <51F721CD.3010006@asianux.com>


For sh, it will report error below:

  [root@dhcp122 linux-next]# make ARCH=sh CROSS_COMPILE=sh-linux-gnu-
  CC      scripts/mod/empty.o
  as: unrecognized option '-little'
  make[2]: *** [scripts/mod/empty.o] Error 2
  make[1]: *** [scripts/mod] Error 2
  make: *** [scripts] Error 2

The related binutils information:

  [root@dhcp122 build-binutils-or32]# rpm -qf /usr/bin/sh-linux-gnu-ld
  binutils-sh-linux-gnu-2.23.51.0.3-1.fc17.x86_64
  [root@dhcp122 build-binutils-or32]# rpm -qf /usr/bin/sh-linux-gnu-as
  binutils-sh-linux-gnu-2.23.51.0.3-1.fc17.x86_64


Is it the binutils's issue ? is the warnings below is the binutils's
issue too? (now, I am downloading related tool chain source code of SH,
and will try again).


Thanks.

On 07/30/2013 10:15 AM, Chen Gang wrote:
> Hello Maintainers:
> 
> When I build sh64 with allmodconfig (without "EXTRA_CFLAGS=-W"), it
> report the warnings below:
> 
>     LD      arch/sh/kernel/cpu/sh5/built-in.o
>   WARNING: arch/sh/kernel/cpu/sh5/built-in.o (.cranges): unexpected non-allocatable section.
>   Did you forget to use "ax"/"aw" in a .S file?
>   Note that for example <linux/init.h> contains
>   section definitions for use in .S files.
> 
> Can it cause real world issue ?
> 
> Welcome any members suggestions or completions.
> 
> 
> Thanks.
> --
> Chen Gang.
> 


-- 
Chen Gang

  reply	other threads:[~2013-07-30  6:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-30  2:15 [Suggestion] sh64: kernel: about the warning: "unexpected non-allocatable section" Chen Gang
2013-07-30  6:09 ` Chen Gang [this message]
2013-07-30  6:11 ` Chen Gang
2013-07-31  7:38 ` Chen Gang
2013-08-01  5:58 ` 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=51F758A5.9010400@asianux.com \
    --to=gang.chen@asianux.com \
    --cc=linux-sh@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