From: Kamalesh Babulal <kamalesh@linux.vnet.ibm.com>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
linux-ia64@vger.kernel.org, Andy Whitcroft <apw@shadowen.org>
Subject: Re: [BUILD-FAILURE] linux-next: Tree for June 11 - on ia64
Date: Wed, 11 Jun 2008 22:16:26 +0530 [thread overview]
Message-ID: <48500162.3060604@linux.vnet.ibm.com> (raw)
In-Reply-To: <20080611145057.GA10487@uranus.ravnborg.org>
Sam Ravnborg wrote:
> On Wed, Jun 11, 2008 at 08:02:14PM +0530, Kamalesh Babulal wrote:
>> Hi Stephen,
>>
>> The next-20080611 kernel build fails on ia64 machine
>>
>> AR arch/ia64/lib/lib.a
>> LD vmlinux.o
>> MODPOST vmlinux.o
>> GEN .version
>> CHK include/linux/compile.h
>> UPD include/linux/compile.h
>> CC init/version.o
>> LD init/built-in.o
>> LD .tmp_vmlinux
>> LD vmlinux
>> ld: .tmp_kallsyms.o: linking constant-gp files with non-constant-gp files
>> ld: failed to merge target specific data of file .tmp_kallsyms.o
>> make: *** [vmlinux] Error 1
>
> A kbuild bug..
> We do a local build of .tmp_kallsyms.o and we do not pass -mconstant-gp
>
> Can you please try if the following patch fixes it.
>
> Sam
Hi Sam,
Thanks, the patch fixes the build failure.
Tested-by: Kamalesh Babulal <kamalesh@linux.vnet.ibm.com>
>
> diff --git a/scripts/link-vmlinux.sh b/scripts/link-vmlinux.sh
> index b9ecff5..b335700 100644
> --- a/scripts/link-vmlinux.sh
> +++ b/scripts/link-vmlinux.sh
> @@ -128,7 +128,7 @@ if [ "${CONFIG_KALLSYMS}" = "y" ]; then
>
> # Do an extra pass to link in kallsyms data
> ${NM} -n .tmp_vmlinux | scripts/kallsyms > .tmp_kallsyms.S
> - ${CC} ${KBUILD_AFLAGS} ${KBUILD_CPPFLAGS} -c -o .tmp_kallsyms.o \
> + ${CC} ${KBUILD_AFLAGS} ${AFLAGS_KERNEL} ${KBUILD_CPPFLAGS} -c -o .tmp_kallsyms.o \
> .tmp_kallsyms.S
> # link in kalll symbols
> tell LD vmlinux
> --
--
Thanks & Regards,
Kamalesh Babulal,
Linux Technology Center,
IBM, ISTL.
next prev parent reply other threads:[~2008-06-11 16:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-11 9:38 linux-next: Tree for June 11 Stephen Rothwell
2008-06-11 14:32 ` [BUILD-FAILURE] linux-next: Tree for June 11 - on ia64 Kamalesh Babulal
2008-06-11 14:50 ` Sam Ravnborg
2008-06-11 16:46 ` Kamalesh Babulal [this message]
2008-06-11 23:10 ` Stephen Rothwell
2008-06-11 23:14 ` Stephen Rothwell
2008-06-11 18:55 ` linux-next: Tree for June 11 Greg KH
2008-06-12 0:05 ` ldp/staging/driver-core (Was: Re: linux-next: Tree for June 11) Stephen Rothwell
2008-06-12 0:17 ` Greg KH
2008-06-12 0:17 ` linux-next: Tree for June 11 Kevin Winchester
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=48500162.3060604@linux.vnet.ibm.com \
--to=kamalesh@linux.vnet.ibm.com \
--cc=apw@shadowen.org \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sam@ravnborg.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).