From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: Claudio Fontana <cfontana@suse.de>,
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 16:03:36 +0100 [thread overview]
Message-ID: <76bb34a6-d12a-5909-04b0-fbc6dcf71e4f@redhat.com> (raw)
In-Reply-To: <42de1769-e1c3-0486-b434-88813aec8ef4@suse.de>
On 3/18/21 10:16 AM, Claudio Fontana wrote:
> 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.
I'm having a slightly different one:
$ make check-block
/home/phil/.local/bin/meson introspect --targets --tests --benchmarks |
/usr/bin/python3 -B scripts/mtest2make.py > Makefile.mtest
GIT ui/keycodemapdb tests/fp/berkeley-testfloat-3
tests/fp/berkeley-softfloat-3 dtc capstone slirp
No such file: tests/qemu-iotests/../../qemu-img
make: *** [/home/phil/source/qemu/tests/Makefile.include:148:
check-block] Error 1
Apparently I was luckier because still having an old socket_scm_helper
built, not sure this is a good thing or not...
$ ls -l tests/qemu-iotests/socket_scm_helper
-rwxr-xr-x. 1 phil root 28824 Mar 3 15:50
tests/qemu-iotests/socket_scm_helper
prev parent reply other threads:[~2021-03-18 15:14 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
2021-03-18 10:03 ` Paolo Bonzini
2021-03-23 12:44 ` Claudio Fontana
2021-03-18 15:03 ` Philippe Mathieu-Daudé [this message]
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=76bb34a6-d12a-5909-04b0-fbc6dcf71e4f@redhat.com \
--to=philmd@redhat.com \
--cc=armbru@redhat.com \
--cc=cfontana@suse.de \
--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).