From: Claudio Fontana <cfontana@suse.de>
To: Markus Armbruster <armbru@redhat.com>, qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
qemu-block@nongnu.org, Max Reitz <mreitz@redhat.com>
Subject: Re: "make check" broken with everything but tools disabled
Date: Thu, 18 Mar 2021 10:16:04 +0100 [thread overview]
Message-ID: <42de1769-e1c3-0486-b434-88813aec8ef4@suse.de> (raw)
In-Reply-To: <877dm7jkib.fsf@dusky.pond.sub.org>
On 3/16/21 2:28 PM, Markus Armbruster wrote:
> Watch this:
>
> $ mkdir bld-tools
> $ cd bld-tools
> $ ../configure --disable-system --disable-user --enable-tools
> $ make check
> [...]
> make: *** No rule to make target 'tests/qemu-iotests/socket_scm_helper', needed by 'check-block'. Stop.
>
>
Hi Markus,
I can reproduce this error too.
When looking at the sequence of commands I was almost sure it was due to a missing "make" before the "make check",
as my experience with the new build system (meson-based), is that I have to do:
make
first, and then
make check
later, or bugs start happening, build can end up doing the wrong things.
I thought this was a known limitation and I am currently just dealing with it.
But then I tried to apply this to your specific case, and I get the same error nevertheless.
make: *** No rule to make target 'tests/qemu-iotests/socket_scm_helper', needed by 'check-block'. Stop.
Ciao,
CLaudio
next prev parent reply other threads:[~2021-03-18 9:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-16 13:28 "make check" broken with everything but tools disabled Markus Armbruster
2021-03-17 22:35 ` John Snow
2021-03-18 8:48 ` Philippe Mathieu-Daudé
2021-03-18 9:16 ` Claudio Fontana [this message]
2021-03-18 10:03 ` Paolo Bonzini
2021-03-23 12:44 ` Claudio Fontana
2021-03-18 15:03 ` Philippe Mathieu-Daudé
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=42de1769-e1c3-0486-b434-88813aec8ef4@suse.de \
--to=cfontana@suse.de \
--cc=armbru@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-block@nongnu.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).