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: Wed, 31 Jul 2013 07:38:38 +0000	[thread overview]
Message-ID: <51F8BEFE.7000605@asianux.com> (raw)
In-Reply-To: <51F721CD.3010006@asianux.com>

On 07/30/2013 02:11 PM, Chen Gang wrote:
> On 07/30/2013 02:09 PM, Chen Gang wrote:
>>
>> 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
>>
> 

It is really the original sh-linux-gnu- compiler's issue (not only for
allmodconfig, but also for sh own config files).

With my new build cross-compiler, It can work for sh architecture own
config files, but can not work with allmodconfig (I will analyze it).

The cross-tools which I build is:

[root@dhcp122 linux-next]# sh3-gchen-linux-gnu-ld -v
GNU ld (crosstool-NG hg+unknown-20130731.103227) 2.22
[root@dhcp122 linux-next]# sh3-gchen-linux-gnu-gcc -v
Using built-in specs.
COLLECT_GCC=sh3-gchen-linux-gnu-gcc
COLLECT_LTO_WRAPPER=/home/gchen/x-tools/sh3-gchen-linux-gnu/bin/../libexec/gcc/sh3-gchen-linux-gnu/4.8.0/lto-wrapper
Target: sh3-gchen-linux-gnu
Configured with: /root/src/toolchain_sh/crosstool-ng-2685dfa9de14/.build/src/gcc-4.8.0/configure --build=x86_64-build_unknown-linux-gnu --host=x86_64-build_unknown-linux-gnu --target=sh3-gchen-linux-gnu --prefix=/root/src/toolchain_sh/crosstool-ng-2685dfa9de14/.build/sh3-gchen-linux-gnu/buildtools --with-local-prefix=/home/gchen/x-tools/sh3-gchen-linux-gnu/sh3-gchen-linux-gnu/sysroot --disable-libmudflap --with-sysroot=/home/gchen/x-tools/sh3-gchen-linux-gnu/sh3-gchen-linux-gnu/sysroot --enable-shared --with-pkgversion='crosstool-NG hg+unknown-20130731.103227' --enable-__cxa_atexit --with-gmp=/root/src/toolchain_sh/crosstool-ng-2685dfa9de14/.build/sh3-gchen-linux-gnu/buildtools --with-mpfr=/root/src/toolchain_sh/crosstool-ng-2685dfa9de14/.build/sh3-gchen-linux-gnu/buildtools --with-mpc=/root/src/toolchain_sh/crosstool-ng-2685dfa9de14/.build/sh3-gchen-linux-gnu/buildtools --with-isl=/root/src/toolchain_sh/crosstool-ng-2685dfa9de14/.build/sh3-gchen-linux-gnu/buildtools --with-c
 loog=/roo
t/src/toolchain_sh/crosstool-ng-2685dfa9de14/.build/sh3-gchen-linux-gnu/buildtools --with-libelf=/root/src/toolchain_sh/crosstool-ng-2685dfa9de14/.build/sh3-gchen-linux-gnu/buildtools --enable-lto --enable-target-optspace --disable-libgomp --disable-libmudflap --disable-nls --disable-multilib --enable-languages=c
Thread model: posix
gcc version 4.8.0 (crosstool-NG hg+unknown-20130731.103227) 


Next, I will make a confirmation for sh64 compiler whether is OK or not.

Welcome any members' suggestions or completions.

Thanks.

> OH, sorry, for sh64, the related information is
> 
>   [root@dhcp122 build-binutils-or32]# rpm -qf /usr/bin/sh64-linux-gnu-as 
>   binutils-sh64-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

  parent reply	other threads:[~2013-07-31  7:38 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
2013-07-30  6:11 ` Chen Gang
2013-07-31  7:38 ` Chen Gang [this message]
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=51F8BEFE.7000605@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