From: Fam Zheng <famz@redhat.com>
To: "Philippe Mathieu-Daudé" <f4bug@amsat.org>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] make check-help not working
Date: Thu, 10 Aug 2017 16:42:55 +0800 [thread overview]
Message-ID: <20170810084255.GA7003@lemon.lan> (raw)
In-Reply-To: <16148252-7ec9-bc6f-023f-d0c12efc2444@amsat.org>
On Fri, 07/28 20:56, Philippe Mathieu-Daudé wrote:
> I'm a bit lost with this error:
>
> (master)$ make check-help V=1
> cc -nostdlib -o check-help.mo
> cc: fatal error: no input files
> compilation terminated.
> rules.mak:115: recipe for target 'check-help.mo' failed
> make: *** [check-help.mo] Error 1
I think this is because in Makefile:
ifneq ($(wildcard config-host.mak),)
include $(SRC_PATH)/tests/Makefile.include
endif
which basically means only include that file, which contains the "check-help"
rule, after configure.
We can move that ifned/endif pair down to tests/Makefile.include and move
check-help out of it.
I'll send a patch for it.
Fam
prev parent reply other threads:[~2017-08-10 8:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-28 23:56 [Qemu-devel] make check-help not working Philippe Mathieu-Daudé
2017-08-10 8:42 ` Fam Zheng [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=20170810084255.GA7003@lemon.lan \
--to=famz@redhat.com \
--cc=f4bug@amsat.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).