From: Michael Neuling <mikey@neuling.org>
To: Chen Gang <gang.chen@asianux.com>, sfr@canb.auug.org.au
Cc: matt@ozlabs.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"paulus@samba.org" <paulus@samba.org>,
imunsie@au1.ibm.com, linuxppc-dev@lists.ozlabs.org
Subject: Re: [Suggestion] PowerPC: kernel: cross compiling issue with allmodconfig
Date: Fri, 15 Mar 2013 15:52:54 +1100 [thread overview]
Message-ID: <25841.1363323174@ale.ozlabs.ibm.com> (raw)
In-Reply-To: <51428C81.6000204@asianux.com>
> do next-* tree support powerpc POWER7 with allmodconfig ?
>
> I met an issue, can we bear it (or I need additional trying) ?
>
>
> Compiling:
> make V=1 EXTRA_CFLAGS=-W ARCH=powerpc allmodconfig
> set cpu type POWER7 in menuconfig.
> set cross-compiler in menuconfig.
> under Fedora 16 x86_64 laptop
> /usr/bin/powerpc64-linux-gnu-gcc -v
> gcc version 4.7.1 20120606 (Red Hat 4.7.1-0.1.20120606) (GCC)
>
> Issue:
> error:
> /android/public-kernel/linux-next/arch/powerpc/kernel/exceptions-64s.S: Assembler messages:
> /android/public-kernel/linux-next/arch/powerpc/kernel/exceptions-64s.S:1304: Error: attempt to move .org backwards
>
> command:
> powerpc64-linux-gnu-gcc -m64 -Wp,-MD,arch/powerpc/kernel/.head_64.o.d -nostdinc -isystem /usr/lib/gcc/powerpc64-linux-gnu/4.7.1/include -I/android/public-kernel/linux-next/arch/powerpc/include -Iarch/powerpc/include/generated -I/android/public-kernel/linux-next/include -Iinclude -I/android/public-kernel/linux-next/arch/powerpc/include/uapi -Iarch/powerpc/include/generated/uapi -I/android/public-kernel/linux-next/include/uapi -Iinclude/generated/uapi -include /android/public-kernel/linux-next/include/linux/kconfig.h -D__KERNEL__ -I/android/public-kernel/linux-next/arch/powerpc -Iarch/powerpc -D__ASSEMBLY__ -I/android/public-kernel/linux-next/arch/powerpc -Iarch/powerpc -Wa,-maltivec -gdwarf-2 -c -o arch/powerpc/kernel/head_64.o /android/public-kernel/linux-next/arch/powerpc/kernel/head_64.S
>
> (head_64.S includes exceptions-64.S)
Yep it's a known problem but no one has bothered to fix it since it
doesn't happen in a config that anyone cares about like
pseries_defconfig and ppc64_defconfig. We've been moving code around in
this area a lot recently hence the breakage.
It should be fixed though. Patches welcome. :-)
Mikey
next prev parent reply other threads:[~2013-03-15 4:52 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-15 2:50 [Suggestion] PowerPC: kernel: cross compiling issue with allmodconfig Chen Gang
2013-03-15 4:52 ` Michael Neuling [this message]
2013-03-15 5:14 ` Chen Gang
2013-03-21 5:55 ` Chen Gang
[not found] ` <514AC418.1070806@gmail.com>
2013-03-21 12:38 ` Benjamin Herrenschmidt
2013-03-22 6:46 ` Chen Gang
2013-03-21 23:21 ` Michael Neuling
2013-03-22 19:17 ` Yoder Stuart-B08248
2013-03-23 2:51 ` Chen Gang F T
2013-03-21 22:54 ` Michael Neuling
2013-03-22 6:55 ` Chen Gang
2013-03-25 0:03 ` Michael Neuling
2013-03-25 1:07 ` Chen Gang
2013-03-25 1:31 ` [PATCH] PowerPC:kernel: make additional room in exception vector area Chen Gang
2013-03-25 5:14 ` Stephen Rothwell
2013-03-25 5:38 ` Chen Gang
2013-03-25 6:07 ` Michael Neuling
2013-03-25 6:20 ` Stephen Rothwell
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=25841.1363323174@ale.ozlabs.ibm.com \
--to=mikey@neuling.org \
--cc=gang.chen@asianux.com \
--cc=imunsie@au1.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=matt@ozlabs.org \
--cc=paulus@samba.org \
--cc=sfr@canb.auug.org.au \
/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;
as well as URLs for NNTP newsgroup(s).