All of lore.kernel.org
 help / color / mirror / Atom feed
From: Olaf Hering <olaf@aepfle.de>
To: Jan Beulich <JBeulich@suse.com>
Cc: xen-devel@lists.xen.org
Subject: Re: qemu-xen fails to build in staging
Date: Wed, 7 Feb 2018 11:13:22 +0100	[thread overview]
Message-ID: <20180207111322.48639c54.olaf@aepfle.de> (raw)
In-Reply-To: <5A7ADB7702000078001A5F4B@prv-mh.provo.novell.com>


[-- Attachment #1.1: Type: text/plain, Size: 710 bytes --]

Am Wed, 07 Feb 2018 02:56:55 -0700
schrieb "Jan Beulich" <JBeulich@suse.com>:

> 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 nor 'git archive' does not take that into account, as a result the "checkout" is incomplete. Great...

/xen-staging $ find -name .git
./.git
./tools/firmware/seabios-dir-remote/.git
./tools/qemu-xen-traditional-dir-remote/.git
./tools/qemu-xen-dir-remote/.git
./tools/qemu-xen-dir-remote/capstone/.git
./tools/qemu-xen-dir-remote/dtc/.git
./tools/qemu-xen-dir-remote/ui/keycodemapdb/.git

Olaf

[-- Attachment #1.2: Digitale Signatur von OpenPGP --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

[-- Attachment #2: Type: text/plain, Size: 157 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

  reply	other threads:[~2018-02-07 10:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-07  8:18 qemu-xen fails to build in staging Olaf Hering
2018-02-07  9:56 ` Jan Beulich
2018-02-07 10:13   ` Olaf Hering [this message]
2018-02-07 12:40     ` Olaf Hering
2018-02-07 12:46       ` Jan Beulich
2018-02-07 14:44       ` Anthony PERARD
2018-02-07 15:23         ` Anthony PERARD

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=20180207111322.48639c54.olaf@aepfle.de \
    --to=olaf@aepfle.de \
    --cc=JBeulich@suse.com \
    --cc=xen-devel@lists.xen.org \
    /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.