public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Prerna Saxena <prerna@linux.vnet.ibm.com>
To: Sasha Levin <levinsasha928@gmail.com>
Cc: Pekka Enberg <penberg@kernel.org>,
	KVM General <kvm@vger.kernel.org>,
	Michael Ellerman <michael@ellerman.id.au>,
	Sasha Levin <sasha.levin@oracle.com>
Subject: Re: kvmtool : [PATCH] PowerPc : Fix compilation for ppc64
Date: Thu, 11 Apr 2013 22:23:06 +0530	[thread overview]
Message-ID: <5166EA72.3020004@linux.vnet.ibm.com> (raw)
In-Reply-To: <CA+1xoqfEVC=8HgRV6dzMdN0ekPnrHw=YEzpuhaj4801x9Vp5Og@mail.gmail.com>

On 04/10/2013 09:05 PM, Sasha Levin wrote:
> Hm, what would LD create before this patch? I thought that the default
> would be to create a binary that corresponds to the platform you're
> building in, so if you build on ppc64 you'd get ppc64 binaries, no?
> 

Hi Sasha,
Thanks for the prompt response.
Powerpc had historically supported 32 bit userspace on a 64 bit kernel,
before everything moved 64 bit.

I'd hit this issue since the default output of 'ld' was turning out to
be 'elf32-powerpc' on my ppc64 build machine. This was running ld-2.22.
I found that adding '--oformat=elf64-powerpc' to the Makefile helped me
tide over it, so I sent a patch to that end.
Today, I verified on another ppc64 machine that ld is automatically
choosing 'elf64-powerpc'. This machine is running 'ld-2.23'

So, this patch can be ignored, since it appears to be a toolchain
dependency. Or, we could put it in place, to ensure kvmtool builds dont
break even if the toolchain is not perfectly configured.
As you suggest :)

Regards,
Prerna

> 
> 
> On Wed, Apr 10, 2013 at 2:44 AM, Pekka Enberg <penberg@kernel.org
> <mailto:penberg@kernel.org>> wrote:
> 
>     On Tue, Apr 9, 2013 at 8:29 PM, Prerna Saxena
>     <prerna@linux.vnet.ibm.com <mailto:prerna@linux.vnet.ibm.com>> wrote:
>     > 'lkvm' compilation on ppc64 fails with the following error :
>     > ...[snip]..
>     >   LINK     guest/init
>     >   LINK     lkvm
>     > /usr/bin/ld: powerpc:common architecture of input file
>     `guest/guest_init.o'
>     > is incompatible with powerpc:common64 output
>     > collect2: ld returned 1 exit status
>     > make: *** [lkvm] Error 1
>     >
>     > This patch corrects the error above, and enables 'lkvm' to compile
>     on ppc64
>     > architecture.
>     >
>     > Signed-off-by: Prerna Saxena <prerna@linux.vnet.ibm.com
>     <mailto:prerna@linux.vnet.ibm.com>>
>     > ---
>     >  tools/kvm/Makefile |    4 ++++
>     >  1 file changed, 4 insertions(+)
>     >
>     > diff --git a/tools/kvm/Makefile b/tools/kvm/Makefile
>     > index 0c59faa..269e29e 100644
>     > --- a/tools/kvm/Makefile
>     > +++ b/tools/kvm/Makefile
>     > @@ -335,7 +335,11 @@ $(PROGRAM_ALIAS): $(PROGRAM)
>     >  $(GUEST_INIT): guest/init.c
>     >         $(E) "  LINK    " $@
>     >         $(Q) $(CC) -static guest/init.c -o $@
>     > +ifeq ($(ARCH), powerpc)
>     > +       $(Q) $(LD) -r -b binary --oformat elf64-powerpc -o
>     guest/guest_init.o $(GUEST_INIT)
>     > +else
>     >         $(Q) $(LD) -r -b binary -o guest/guest_init.o $(GUEST_INIT)
>     > +endif
>     >
>     >  $(DEPS):
>     >
>     > --
>     > 1.7.10.4
> 
>     Michael, Sasha, comments?
>     --
>     To unsubscribe from this list: send the line "unsubscribe kvm" in
>     the body of a message to majordomo@vger.kernel.org
>     <mailto:majordomo@vger.kernel.org>
>     More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 
> 


-- 
Prerna Saxena

Linux Technology Centre,
IBM Systems and Technology Lab,
Bangalore, India


  parent reply	other threads:[~2013-04-11 16:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-09 17:29 kvmtool : [PATCH] PowerPc : Fix compilation for ppc64 Prerna Saxena
2013-04-10  6:44 ` Pekka Enberg
     [not found]   ` <CA+1xoqfEVC=8HgRV6dzMdN0ekPnrHw=YEzpuhaj4801x9Vp5Og@mail.gmail.com>
2013-04-11 16:53     ` Prerna Saxena [this message]
2013-04-11 19:44       ` Sasha Levin

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=5166EA72.3020004@linux.vnet.ibm.com \
    --to=prerna@linux.vnet.ibm.com \
    --cc=kvm@vger.kernel.org \
    --cc=levinsasha928@gmail.com \
    --cc=michael@ellerman.id.au \
    --cc=penberg@kernel.org \
    --cc=sasha.levin@oracle.com \
    /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