On Wed, Feb 07, 2018 at 02:44:05PM +, Anthony PERARD wrote:
> On Wed, Feb 07, 2018 at 01:40:04PM +0100, Olaf Hering wrote:
> > Am Wed, 7 Feb 2018 11:13:22 +0100
> > schrieb Olaf Hering :
> >
> > > Yes, it looks like qemu has now submodules which are required for build.
> >
>
On Wed, Feb 07, 2018 at 01:40:04PM +0100, Olaf Hering wrote:
> Am Wed, 7 Feb 2018 11:13:22 +0100
> schrieb Olaf Hering :
>
> > Yes, it looks like qemu has now submodules which are required for build.
>
> How is the required state of the submodules tracked?
Hi,
QEMU have now a
>>> On 07.02.18 at 13:40, wrote:
> Am Wed, 7 Feb 2018 11:13:22 +0100
> schrieb Olaf Hering :
>
>> Yes, it looks like qemu has now submodules which are required for build.
>
> How is the required state of the submodules tracked? When I did a local
> build I got
Am Wed, 7 Feb 2018 11:13:22 +0100
schrieb Olaf Hering :
> Yes, it looks like qemu has now submodules which are required for build.
How is the required state of the submodules tracked? When I did a local build I
got 10739aa from qemu.org, and building xen.git#staging succeeds.
Am Wed, 07 Feb 2018 02:56:55 -0700
schrieb "Jan Beulich" :
> I think I had seen this too, and only then I realized that now I need
> to set up the respective submodule in the qemu tree.
Yes, it looks like qemu has now submodules which are required for build.
Neither configure
>>> On 07.02.18 at 09:18, wrote:
> With current staging, qemu-xen fails to build. It looks like a ordering
> issue, I assume ui/input-keymap-linux-to-qcode.c is a generated file.
> It is (as always) a fresh clean checkout in a clean chroot.
I think I had seen this too, and only
With current staging, qemu-xen fails to build. It looks like a ordering
issue, I assume ui/input-keymap-linux-to-qcode.c is a generated file.
It is (as always) a fresh clean checkout in a clean chroot.
[ 505s]