> On 21 Apr 2015, at 12:06, George Dunlap wrote:
>
> On 04/21/2015 12:04 PM, Dave Scott wrote:
>>> FYI I’ve been sporadically building the blktap userspace on ARM and it
>>> seems to work, although last time I had to fix some format strings which
>>> assumed a 64-bit architecture. I think that
On 04/21/2015 12:04 PM, Dave Scott wrote:
>> FYI I’ve been sporadically building the blktap userspace on ARM and it seems
>> to work, although last time I had to fix some format strings which assumed a
>> 64-bit architecture. I think that patch got merged. I think my last build
>> was in January
> On 21 Apr 2015, at 12:01, Dave Scott wrote:
>
>>
>> On 21 Apr 2015, at 11:42, Stefano Stabellini
>> wrote:
>>
>> On Tue, 21 Apr 2015, George Dunlap wrote:
>>> On 04/21/2015 11:09 AM, Stefano Stabellini wrote:
On Tue, 21 Apr 2015, George Dunlap wrote:
> On 04/21/2015 10:25 AM, Ian
> On 21 Apr 2015, at 11:42, Stefano Stabellini
> wrote:
>
> On Tue, 21 Apr 2015, George Dunlap wrote:
>> On 04/21/2015 11:09 AM, Stefano Stabellini wrote:
>>> On Tue, 21 Apr 2015, George Dunlap wrote:
On 04/21/2015 10:25 AM, Ian Campbell wrote:
> On Mon, 2015-04-20 at 18:05 +0100, Stef
On 04/21/2015 11:42 AM, Stefano Stabellini wrote:
>> The only reason to disable this on ARM at the minute is because you
>> *believe* that nobody will ever want to build the blktap2 kernel module
>> on ARM, and so you want to avoid the build overhead and space overhead
>> of compiling and using dea
On Tue, 21 Apr 2015, George Dunlap wrote:
> On 04/21/2015 11:09 AM, Stefano Stabellini wrote:
> > On Tue, 21 Apr 2015, George Dunlap wrote:
> >> On 04/21/2015 10:25 AM, Ian Campbell wrote:
> >>> On Mon, 2015-04-20 at 18:05 +0100, Stefano Stabellini wrote:
> >> I think we need to disable the bui
On 04/21/2015 11:09 AM, Stefano Stabellini wrote:
> On Tue, 21 Apr 2015, George Dunlap wrote:
>> On 04/21/2015 10:25 AM, Ian Campbell wrote:
>>> On Mon, 2015-04-20 at 18:05 +0100, Stefano Stabellini wrote:
>> I think we need to disable the build on architectures other than x86,
>> see grub
On Tue, 21 Apr 2015, George Dunlap wrote:
> On 04/21/2015 10:25 AM, Ian Campbell wrote:
> > On Mon, 2015-04-20 at 18:05 +0100, Stefano Stabellini wrote:
> I think we need to disable the build on architectures other than x86,
> see grub for example
> >
> > Eventually we might want to buil
On Tue, 21 Apr 2015, Ian Campbell wrote:
> On Mon, 2015-04-20 at 18:05 +0100, Stefano Stabellini wrote:
> > > > I think we need to disable the build on architectures other than x86,
> > > > see grub for example
>
> Eventually we might want to build our own grub on ARM in order to pick
> up Fu Wei'
On 04/21/2015 10:25 AM, Ian Campbell wrote:
> On Mon, 2015-04-20 at 18:05 +0100, Stefano Stabellini wrote:
I think we need to disable the build on architectures other than x86,
see grub for example
>
> Eventually we might want to build our own grub on ARM in order to pick
> up Fu Wei's m
On Mon, 2015-04-20 at 18:05 +0100, Stefano Stabellini wrote:
> > > I think we need to disable the build on architectures other than x86,
> > > see grub for example
Eventually we might want to build our own grub on ARM in order to pick
up Fu Wei's multiboot for arm64 patches, until they enter distr
On Mon, 20 Apr 2015, George Dunlap wrote:
> On 04/17/2015 11:58 AM, Stefano Stabellini wrote:
> > On Thu, 16 Apr 2015, George Dunlap wrote:
> >> Until we start hosting the blktap repo on xenbits, use the one from github.
> >>
> >> Also, we need to pass in the directories where to find the
> >> libb
On 04/17/2015 11:58 AM, Stefano Stabellini wrote:
> On Thu, 16 Apr 2015, George Dunlap wrote:
>> Until we start hosting the blktap repo on xenbits, use the one from github.
>>
>> Also, we need to pass in the directories where to find the
>> libblktapctl headers in the Xen build.
>>
>> Signed-off-by
On Mon, 20 Apr 2015, George Dunlap wrote:
> On 04/17/2015 11:50 AM, Stefano Stabellini wrote:
> > On Thu, 16 Apr 2015, George Dunlap wrote:
> >> Until we start hosting the blktap repo on xenbits, use the one from github.
> >>
> >> Also, we need to pass in the directories where to find the
> >> libb
On 04/17/2015 11:50 AM, Stefano Stabellini wrote:
> On Thu, 16 Apr 2015, George Dunlap wrote:
>> Until we start hosting the blktap repo on xenbits, use the one from github.
>>
>> Also, we need to pass in the directories where to find the
>> libblktapctl headers in the Xen build.
>>
>> Signed-off-by
On Fri, 2015-04-17 at 11:50 +0100, Stefano Stabellini wrote:
> > +local DEP_CentOS_x86_32="$DEP_Redhat_common"
> > +local DEP_CentOS_x86_64="$DEP_Redhat_x86_32"
>
> Redhat? I don't know no Redhat.
Is the use of x86_32 rather than common on the x86_64 case deliberate?
Ian.
On Thu, 16 Apr 2015, George Dunlap wrote:
> Until we start hosting the blktap repo on xenbits, use the one from github.
>
> Also, we need to pass in the directories where to find the
> libblktapctl headers in the Xen build.
>
> Signed-off-by: George Dunlap
> ---
> Note: For now use the "upstream
On Thu, 16 Apr 2015, George Dunlap wrote:
> Until we start hosting the blktap repo on xenbits, use the one from github.
>
> Also, we need to pass in the directories where to find the
> libblktapctl headers in the Xen build.
>
> Signed-off-by: George Dunlap
> ---
> Note: For now use the "upstream
Until we start hosting the blktap repo on xenbits, use the one from github.
Also, we need to pass in the directories where to find the
libblktapctl headers in the Xen build.
Signed-off-by: George Dunlap
---
Note: For now use the "upstream" XenServer repo.
Also, to build with this you need the p
19 matches
Mail list logo
