From: Boaz Harrosh <bharrosh@panasas.com>
To: Avi Kivity <avi@redhat.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Gregory Haskins <ghaskins@novell.com>
Subject: Re: linux-next: kvm tree build failure
Date: Thu, 21 May 2009 10:48:23 +0300 [thread overview]
Message-ID: <4A150747.3070304@panasas.com> (raw)
In-Reply-To: <4A150515.8030608@redhat.com>
On 05/21/2009 10:39 AM, Avi Kivity wrote:
> Boaz Harrosh wrote:
>>> I'll look for a ppc machine for build testing.
>>>
>>>
>> Can't you cross compile for ppc? I can't remember someone posted a link
>> with binary cross-compiler packages a while back.
>>
>>
>
> I have userspace to test as well, which needs a ton of cross-compiled
> libraries.
>
A cross compiler produces native foreign code. A Native distribution with
binary libraries will work just as well.
Do you mean to set up all the build environment and dependencies?
Perhaps get a ready made ppc linux image, mount and chroot into it
and build that way.
If only you had an emulator for ppc?
Boaz
next prev parent reply other threads:[~2009-05-21 7:48 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-21 7:21 linux-next: kvm tree build failure Stephen Rothwell
2009-05-21 7:32 ` Avi Kivity
2009-05-21 7:37 ` Boaz Harrosh
2009-05-21 7:39 ` Avi Kivity
2009-05-21 7:48 ` Boaz Harrosh [this message]
2009-05-21 10:05 ` Avi Kivity
2009-05-21 13:04 ` [PATCH] kvm: fix irqfd build failure discovered in linux-next Gregory Haskins
2009-05-21 13:10 ` Avi Kivity
2009-05-21 13:26 ` Gregory Haskins
2009-05-21 13:29 ` Avi Kivity
2009-05-21 13:28 ` [PATCH v2] " Gregory Haskins
2009-05-21 13:52 ` Avi Kivity
2009-05-21 14:04 ` Gregory Haskins
-- strict thread matches above, loose matches on Subject: below --
2010-01-19 1:42 linux-next: kvm tree build failure Stephen Rothwell
2010-01-19 7:57 ` Avi Kivity
2010-01-19 9:42 ` Stephen Rothwell
2010-01-11 8:07 Stephen Rothwell
2010-01-11 8:21 ` Stephen Rothwell
2010-01-11 10:27 ` Avi Kivity
2009-08-13 2:58 Stephen Rothwell
2009-08-13 8:58 ` Avi Kivity
2009-06-23 5:53 Stephen Rothwell
2009-06-23 10:23 ` Avi Kivity
2009-06-18 1:11 Stephen Rothwell
2009-06-18 4:25 ` Jaswinder Singh Rajput
2009-06-18 9:49 ` Avi Kivity
2008-12-22 13:25 Stephen Rothwell
2008-12-29 5:17 ` Stephen Rothwell
2009-01-02 0:53 ` Stephen Rothwell
2009-01-04 11:08 ` Avi Kivity
2009-01-04 19:45 ` Hollis Blanchard
2009-01-04 19:55 ` Avi Kivity
2008-12-18 11:05 Stephen Rothwell
2008-10-15 5:47 Stephen Rothwell
2008-10-15 13:25 ` Avi Kivity
2008-09-17 7:01 Stephen Rothwell
2008-09-17 8:50 ` Ingo Molnar
2008-09-24 12:39 ` Avi Kivity
2008-09-24 16:18 ` Jesse Barnes
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=4A150747.3070304@panasas.com \
--to=bharrosh@panasas.com \
--cc=avi@redhat.com \
--cc=ghaskins@novell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.