On Tue, Feb 09, Luis R. Rodriguez wrote:
> The error log from compiling the libSDL test is:
> /tmp/qemu-conf--5604-.c:1:17: fatal error: SDL.h: No such file or directory
This is just the configure test, it can be ignored.
Olaf
___
Xen-devel mailing li
On Tue, 2016-02-09 at 21:44 -0800, Luis R. Rodriguez wrote:
> If I just cd into that directory (tools/qemu-xen-traditional-dir/),
> run ./configure and build it fails with:
This doesn't work/isn't supported. The Xen build system includes support
for recursing properly into qemu-xen-traditional-dir
On Tue, 2016-02-09 at 17:53 +0100, Luis R. Rodriguez wrote:
>
> > > === PCI passthrough capability has been enabled ===
> > > CCqemu-nbd.o
> > > In file included from ./xen-config-host.h:19:0,
> > > from ./config-host.h:18,
> > > from ./qemu-common.h:33,
> >
On Tue, 2016-02-09 at 17:39 +0100, Luis R. Rodriguez wrote:
>
> > I wouldn't bet on it always doing the right thing with 3rd party components
> > like qemu-xen.
>
> Hrm, so how can I get the proper maintainer ? For my case I need to split this
> series up into 5 or 6 series for 5 separate trees:
On Tue, Feb 9, 2016 at 8:39 AM, Ian Campbell wrote:
>> And then:
>>
>> === PCI passthrough capability has been enabled ===
>> CCqemu-nbd.o
>> In file included from ./xen-config-host.h:19:0,
>> from ./config-host.h:18,
>> from ./qemu-common.h:33,
>>
On Tue, Feb 9, 2016 at 8:53 AM, Luis R. Rodriguez wrote:
>> Missing dev package, not a gcc 5 vs 6 issue.
>
> Its odd considering I had been building Xen for a long time without such dev
> packages. Perhaps we don't propagate --disable-gfx-check for on
> tools/qemu-xen-traditional-dir if no such sd
On Tue, 2016-02-09 at 16:22 +, Ian Campbell wrote:
> On Tue, 2016-02-09 at 17:09 +0100, Luis R. Rodriguez wrote:
> > The realization that compilation is not working for some modern
> > tools, in particular for OpenSUSE factory for a long time without
> > it being addressed is a bit concerning.
On Tue, Feb 09, 2016 at 04:39:20PM +, Ian Campbell wrote:
> On Tue, 2016-02-09 at 17:30 +0100, Luis R. Rodriguez wrote:
> > On Tue, Feb 09, 2016 at 04:22:01PM +, Ian Campbell wrote:
> > > On Tue, 2016-02-09 at 17:09 +0100, Luis R. Rodriguez wrote:
> > > > The realization that compilation is
On Tue, Feb 09, 2016 at 04:26:36PM +, Ian Campbell wrote:
> On Tue, 2016-02-09 at 16:56 +0100, Luis R. Rodriguez wrote:
> >
> > No you're right, this just fell through the cracks. The surprising case of
> > things still being broken on modern tools however should raise a bit of
> > concern eit
On Tue, 2016-02-09 at 17:30 +0100, Luis R. Rodriguez wrote:
> On Tue, Feb 09, 2016 at 04:22:01PM +, Ian Campbell wrote:
> > On Tue, 2016-02-09 at 17:09 +0100, Luis R. Rodriguez wrote:
> > > The realization that compilation is not working for some modern
> > > tools, in particular for OpenSUSE f
On Tue, Feb 09, 2016 at 04:22:01PM +, Ian Campbell wrote:
> On Tue, 2016-02-09 at 17:09 +0100, Luis R. Rodriguez wrote:
> > The realization that compilation is not working for some modern
> > tools, in particular for OpenSUSE factory for a long time without
> > it being addressed is a bit conce
On Tue, 2016-02-09 at 16:56 +0100, Luis R. Rodriguez wrote:
>
> No you're right, this just fell through the cracks. The surprising case of
> things still being broken on modern tools however should raise a bit of
> concern either by opensuse factory folks or by Xen build folks in general.
AFAIK b
On Tue, 2016-02-09 at 17:09 +0100, Luis R. Rodriguez wrote:
> The realization that compilation is not working for some modern
> tools, in particular for OpenSUSE factory for a long time without
> it being addressed is a bit concerning.
I don't know what OpenSUSE factory is building but Xen 4.6.0 b
On Tue, Feb 09, 2016 at 01:08:13AM -0700, Jan Beulich wrote:
> >>> On 06.02.16 at 02:48, wrote:
> > On Fri, Nov 20, 2015 at 9:47 AM, Luis R. Rodriguez
> > wrote:
> >> From: "Luis R. Rodriguez"
> >>
> >> Here's a slew of build fixes as well as build warning fixes
> >> required when using the late
On Mon, Feb 08, 2016 at 09:58:23AM +, Ian Campbell wrote:
> On Fri, 2016-02-05 at 17:48 -0800, Luis R. Rodriguez wrote:
> > What's up folks? How can this process be made smoother, did I do
> > something wrong, what can I do to help better?
>
> When you first sent this series to Jan + me not co
>>> On 06.02.16 at 02:48, wrote:
> On Fri, Nov 20, 2015 at 9:47 AM, Luis R. Rodriguez
> wrote:
>> From: "Luis R. Rodriguez"
>>
>> Here's a slew of build fixes as well as build warning fixes
>> required when using the latest build tools, at least gcc 5 and
>> binutils 2.25.0.
>
> One good reason
On Fri, 2016-02-05 at 17:48 -0800, Luis R. Rodriguez wrote:
> What's up folks? How can this process be made smoother, did I do
> something wrong, what can I do to help better?
When you first sent this series to Jan + me not copying the list you were
asked to send to the list _and_ to CC the approp
Hi Doug,
> > 0 day build tests the kernel all the time, even if my patch gets
> > missed, after a few days other will immediately notice. These days
> > its extremely hard for me to build linux-next and have a build
> > issue.
> >
> > I recommend we push on the momentum to see if we can piggy bac
On 2/5/16 10:07 PM, Luis R. Rodriguez wrote:
> On Fri, Feb 05, 2016 at 10:52:01PM -0500, Konrad Rzeszutek Wilk wrote:
>> On Fri, Feb 05, 2016 at 05:48:37PM -0800, Luis R. Rodriguez wrote:
>>> On Fri, Nov 20, 2015 at 9:47 AM, Luis R. Rodriguez
>>> wrote:
From: "Luis R. Rodriguez"
He
On Fri, Feb 05, 2016 at 10:52:01PM -0500, Konrad Rzeszutek Wilk wrote:
> On Fri, Feb 05, 2016 at 05:48:37PM -0800, Luis R. Rodriguez wrote:
> > On Fri, Nov 20, 2015 at 9:47 AM, Luis R. Rodriguez
> > wrote:
> > > From: "Luis R. Rodriguez"
> > >
> > > Here's a slew of build fixes as well as build w
On Fri, Feb 05, 2016 at 05:48:37PM -0800, Luis R. Rodriguez wrote:
> On Fri, Nov 20, 2015 at 9:47 AM, Luis R. Rodriguez
> wrote:
> > From: "Luis R. Rodriguez"
> >
> > Here's a slew of build fixes as well as build warning fixes
> > required when using the latest build tools, at least gcc 5 and
> >
On Fri, Nov 20, 2015 at 9:47 AM, Luis R. Rodriguez
wrote:
> From: "Luis R. Rodriguez"
>
> Here's a slew of build fixes as well as build warning fixes
> required when using the latest build tools, at least gcc 5 and
> binutils 2.25.0.
One good reason for some folks to get discouraged to work with
From: "Luis R. Rodriguez"
Here's a slew of build fixes as well as build warning fixes
required when using the latest build tools, at least gcc 5 and
binutils 2.25.0. I ran into this while doing development on OpenSUSE
factory. Other rolling distros seem to be having similar issues based
on inspec
23 matches
Mail list logo
