All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: QEMU Developers <qemu-devel@nongnu.org>,
	Michael Roth <michael.roth@amd.com>,
	Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: how to build qemu 8.1 - keycodemapdb?
Date: Wed, 26 Jul 2023 09:50:16 +0100	[thread overview]
Message-ID: <ZMDeSBP7tkYowKV6@redhat.com> (raw)
In-Reply-To: <fc51603b-c89a-c3d5-f59c-c191847c6c1d@tls.msk.ru>

On Wed, Jul 26, 2023 at 10:15:24AM +0300, Michael Tokarev wrote:
> 26.07.2023 09:41, Michael Tokarev wrote:
> 
> > Looks like scripts/make-release.sh needs some updating.

FWIW, i see the same problem as you:

$ ./configure  --target-list=x86_64-softmmu --disable-download
Using './build' as the directory for build output

ERROR: missing subprojects

This is not a GIT checkout but subproject content appears to
be missing. Do not use 'git archive' or GitHub download links
to acquire QEMU source archives. Non-GIT builds are only
supported with source archives linked from:

  https://www.qemu.org/download/#source

Developers working with GIT can use scripts/archive-source.sh
if they need to create valid source archives.


> make-release.sh apparently does the right thing. But the published
> tarball does not include the 3 required sub-projects anyway.
> 
> Is it about how the release is made?  What is used to make the
> actual release tarball, is it not make-release.sh?

make-release is what I expect to be used for making release
tarballs.

With regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|



  reply	other threads:[~2023-07-26  8:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-26  6:20 how to build qemu 8.1 - keycodemapdb? Michael Tokarev
2023-07-26  6:41 ` Michael Tokarev
2023-07-26  7:15   ` Michael Tokarev
2023-07-26  8:50     ` Daniel P. Berrangé [this message]
2023-07-26  9:05       ` Michael Tokarev
2023-07-26  9:18         ` Daniel P. Berrangé
2023-07-26 23:47           ` Michael Roth

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=ZMDeSBP7tkYowKV6@redhat.com \
    --to=berrange@redhat.com \
    --cc=michael.roth@amd.com \
    --cc=mjt@tls.msk.ru \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.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.