From: Sasha Levin <sasha.levin@oracle.com>
To: Prerna Saxena <prerna@linux.vnet.ibm.com>
Cc: Sasha Levin <levinsasha928@gmail.com>,
Pekka Enberg <penberg@kernel.org>,
KVM General <kvm@vger.kernel.org>,
Michael Ellerman <michael@ellerman.id.au>
Subject: Re: kvmtool : [PATCH] PowerPc : Fix compilation for ppc64
Date: Thu, 11 Apr 2013 15:44:15 -0400 [thread overview]
Message-ID: <5167128F.7050806@oracle.com> (raw)
In-Reply-To: <5166EA72.3020004@linux.vnet.ibm.com>
On 04/11/2013 12:53 PM, Prerna Saxena wrote:
> 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 :)
What worries me with about this patch is that it will break build on 32bit
machines.
I don't know if those are even supported these days or not, but if they are -
we need something different to handle that.
Thanks,
Sasha
prev parent reply other threads:[~2013-04-11 19:44 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
2013-04-11 19:44 ` Sasha Levin [this message]
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=5167128F.7050806@oracle.com \
--to=sasha.levin@oracle.com \
--cc=kvm@vger.kernel.org \
--cc=levinsasha928@gmail.com \
--cc=michael@ellerman.id.au \
--cc=penberg@kernel.org \
--cc=prerna@linux.vnet.ibm.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