From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Sam Ravnborg <sam@ravnborg•org>
Cc: Kamalesh Babulal <kamalesh@linux•vnet.ibm.com>,
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: Thu, 12 Jun 2008 09:10:03 +1000 [thread overview]
Message-ID: <20080612091003.775bc671.sfr@canb.auug.org.au> (raw)
In-Reply-To: <484FE1EE.9020201@linux.vnet.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 839 bytes --]
Hi Sam,
One for you?
On Wed, 11 Jun 2008 20:02:14 +0530 Kamalesh Babulal <kamalesh@linux•vnet.ibm.com> wrote:
>
> 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
>
> --
> Thanks & Regards,
> Kamalesh Babulal,
> Linux Technology Center,
> IBM, ISTL.
--
Cheers,
Stephen Rothwell sfr@canb•auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2008-06-11 23:10 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
2008-06-11 23:10 ` Stephen Rothwell [this message]
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=20080612091003.775bc671.sfr@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=apw@shadowen$(echo .)org \
--cc=kamalesh@linux$(echo .)vnet.ibm.com \
--cc=linux-ia64@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sam@ravnborg$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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