From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: Juan Quintela <quintela@redhat.com>
Cc: qemu-devel@nongnu.org, lvivier@redhat.com, peterx@redhat.com
Subject: Re: [Qemu-devel] [PATCH] migration-test: Only generate a single target architecture
Date: Thu, 11 Oct 2018 19:07:23 +0100 [thread overview]
Message-ID: <20181011180723.GE29526@work-vm> (raw)
In-Reply-To: <20180913132313.11370-1-quintela@redhat.com>
* Juan Quintela (quintela@redhat.com) wrote:
> Several changes:
> - We only allow generate header "inside" the tree. Why? Because we
> need to connit the result, so it makes no sense to generate them on
> the build dir.
> - We only generate a single target each time. Getting all the
> cross-compilers correctly is an impossible task. So know you do:
> make -C tests/migration $target (native)
> make CROSS_PREFIX=foo- -C tests/migratiion $target (cross)
> And you are done.
>
> - If we are building out of tree, we have no data about if we are
> cross-compile or whatever. So instead of guess what is happening,
> just do what I pointed on previous point.
>
> Signed-off-by: Juan Quintela <quintela@redhat.com>
Reviewed-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
and queued.
> ---
> tests/migration/Makefile | 23 ++++++++++++++---------
> 1 file changed, 14 insertions(+), 9 deletions(-)
>
> diff --git a/tests/migration/Makefile b/tests/migration/Makefile
> index ff726ed7dd..13e99b1692 100644
> --- a/tests/migration/Makefile
> +++ b/tests/migration/Makefile
> @@ -9,6 +9,19 @@ TARGET_LIST = i386 aarch64 s390x
>
> SRC_PATH = ../..
>
> +.PHONY: help $(TARGET_LIST)
> +help:
> + @echo "Create migration guest includes. We generate a binary."
> + @echo "And then convert that binary to an include file that can be"
> + @echo "run in a guest."
> + @echo "Possible operations are:"
> + @echo
> + @echo " $(MAKE) clean Remove all intermediate files"
> + @echo " $(MAKE) target Generate for that target"
> + @echo " $(MAKE) CROSS_PREFIX=... target"
> + @echo " Cross-compile than target"
> + @echo " Possible targets are: $(TARGET_LIST)"
> +
> override define __note
> /* This file is automatically generated from the assembly file in
> * tests/migration/$@. Edit that file and then run "make all"
> @@ -18,16 +31,8 @@ override define __note
> endef
> export __note
>
> -find-arch-cross-cc = $(lastword $(shell grep -h "CROSS_CC_GUEST=" $(wildcard $(SRC_PATH)/$(patsubst i386,*86*,$(1))-softmmu/config-target.mak) /dev/null))
> -parse-cross-prefix = $(subst gcc,,$(patsubst cc,gcc,$(patsubst CROSS_CC_GUEST="%",%,$(call find-arch-cross-cc,$(1)))))
> -gen-cross-prefix = $(patsubst %-,CROSS_PREFIX=%-,$(call parse-cross-prefix,$(1)))
> -
> -.PHONY: all $(TARGET_LIST)
> -
> -all: $(TARGET_LIST)
> -
> $(TARGET_LIST):
> - $(MAKE) -C $@ $(call gen-cross-prefix,$@)
> + $(MAKE) CROSS_PREFIX=$(CROSS_PREFIX) -C $@
>
> clean:
> for target in $(TARGET_LIST); do \
> --
> 2.17.1
>
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
prev parent reply other threads:[~2018-10-11 18:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-13 13:23 [Qemu-devel] [PATCH] migration-test: Only generate a single target architecture Juan Quintela
2018-09-13 17:06 ` Eric Blake
2018-10-11 18:07 ` Dr. David Alan Gilbert [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=20181011180723.GE29526@work-vm \
--to=dgilbert@redhat.com \
--cc=lvivier@redhat.com \
--cc=peterx@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
/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).