From: Andrew Jones <drjones@redhat.com>
To: Alexander Spyridakis <a.spyridakis@virtualopensystems.com>
Cc: mttcg@greensocs.com, kvm@vger.kernel.org,
claudio.fontana@huawei.com, mark.burton@greensocs.com,
qemu-devel@nongnu.org, a.rigo@virtualopensystems.com,
Jani.Kokkonen@huawei.com, alex.bennee@linaro.org,
fred.konrad@greensocs.com
Subject: Re: [Qemu-devel] [kvm-unit-tests PATCH 2/2] arm/arm64 config: Fix arch_clean rule
Date: Fri, 4 Sep 2015 12:48:35 +0200 [thread overview]
Message-ID: <20150904104835.GC3096@hawk.localdomain> (raw)
In-Reply-To: <1441185926-61587-3-git-send-email-a.spyridakis@virtualopensystems.com>
On Wed, Sep 02, 2015 at 11:25:26AM +0200, Alexander Spyridakis wrote:
> Properly clean any generated object and binary files after a 'make clean',
> this fixes an issue when trying to reconfigure between arm and arm64.
Are you also running configure (with the opposite arch selected) after
'make clean'? If not, then that could be the source of your problems.
Anyway, please describe the issues you're seeing because I don't see
what this patch is doing that isn't already being done. The lines this
patch adds are already there. See the arm_clean target in
config/config-arm-common.mak.
Thanks,
drew
>
> Signed-off-by: Alexander Spyridakis <a.spyridakis@virtualopensystems.com>
> ---
> config/config-arm.mak | 2 ++
> config/config-arm64.mak | 3 ++-
> 2 files changed, 4 insertions(+), 1 deletion(-)
>
> diff --git a/config/config-arm.mak b/config/config-arm.mak
> index ae6c2e7..68fab62 100644
> --- a/config/config-arm.mak
> +++ b/config/config-arm.mak
> @@ -21,3 +21,5 @@ tests =
> include config/config-arm-common.mak
>
> arch_clean: arm_clean
> + $(RM) $(TEST_DIR)/*.o $(TEST_DIR)/*.flat $(TEST_DIR)/*.elf \
> + $(TEST_DIR)/.*.d lib/arm/.*.d
> diff --git a/config/config-arm64.mak b/config/config-arm64.mak
> index d61b703..a0bc1b3 100644
> --- a/config/config-arm64.mak
> +++ b/config/config-arm64.mak
> @@ -17,4 +17,5 @@ tests =
> include config/config-arm-common.mak
>
> arch_clean: arm_clean
> - $(RM) lib/arm64/.*.d
> + $(RM) $(TEST_DIR)/*.o $(TEST_DIR)/*.flat $(TEST_DIR)/*.elf \
> + $(TEST_DIR)/.*.d lib/arm64/.*.d
> --
> 2.1.4
>
>
next prev parent reply other threads:[~2015-09-04 10:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-02 9:25 [Qemu-devel] [kvm-unit-tests PATCH 0/2] arm/arm64: Add self-modifying code test case Alexander Spyridakis
2015-09-02 9:25 ` [Qemu-devel] [kvm-unit-tests PATCH 1/2] arm/arm64: Add self-modifying code test Alexander Spyridakis
2015-09-02 9:25 ` [Qemu-devel] [kvm-unit-tests PATCH 2/2] arm/arm64 config: Fix arch_clean rule Alexander Spyridakis
2015-09-04 10:48 ` Andrew Jones [this message]
2015-09-04 13:48 ` Alexander Spyridakis
2015-09-04 14:05 ` Andrew Jones
2015-09-04 14:18 ` Peter Maydell
2015-09-04 14:53 ` Alexander Spyridakis
2015-09-07 13:35 ` Alexander Spyridakis
2015-09-07 14:37 ` Andrew Jones
2015-09-07 14:59 ` Alexander Spyridakis
2015-09-04 13:53 ` Alexander Spyridakis
2015-09-04 14:08 ` Andrew Jones
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=20150904104835.GC3096@hawk.localdomain \
--to=drjones@redhat.com \
--cc=Jani.Kokkonen@huawei.com \
--cc=a.rigo@virtualopensystems.com \
--cc=a.spyridakis@virtualopensystems.com \
--cc=alex.bennee@linaro.org \
--cc=claudio.fontana@huawei.com \
--cc=fred.konrad@greensocs.com \
--cc=kvm@vger.kernel.org \
--cc=mark.burton@greensocs.com \
--cc=mttcg@greensocs.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 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).