From: "Philippe Mathieu-Daudé" <f4bug@amsat.org>
To: John Arbuckle <programmingkidx@gmail.com>,
Peter Maydell <peter.maydell@linaro.org>,
Paolo Bonzini <pbonzini@redhat.com>
Cc: "Philippe Mathieu-Daudé" <f4bug@amsat.org>,
"Yongbok Kim" <yongbok.kim@imgtec.com>,
"James Hogan" <james.hogan@imgtec.com>,
"Aurelien Jarno" <aurelien@aurel32.net>,
"Peter Crosthwaite" <crosthwaite.peter@gmail.com>,
"Juan Quintela" <quintela@redhat.com>,
qemu-devel@nongnu.org
Subject: [Qemu-devel] [PATCH for 2.10 2/4] fdt: check fdt_required condition can be satisfied _after_ testing libfdt
Date: Wed, 26 Jul 2017 18:40:08 -0300 [thread overview]
Message-ID: <20170726214010.420-3-f4bug@amsat.org> (raw)
In-Reply-To: <20170726214010.420-1-f4bug@amsat.org>
Signed-off-by: Philippe Mathieu-Daudé <f4bug@amsat.org>
---
configure | 18 +++++++++---------
1 file changed, 9 insertions(+), 9 deletions(-)
diff --git a/configure b/configure
index 063de32773..0d5bdb3ae9 100755
--- a/configure
+++ b/configure
@@ -3558,15 +3558,6 @@ for target in $target_list; do
esac
done
-if test "$fdt_required" = "yes"; then
- if test "$fdt" = "no"; then
- error_exit "fdt disabled but some requested targets require it." \
- "You can turn off fdt only if you also disable all the system emulation" \
- "targets which need it (by specifying a cut down --target-list)."
- fi
- fdt=yes
-fi
-
if test "$fdt" != "no" ; then
fdt_libs="-lfdt"
# explicitly check for libfdt_env.h as it is missing in some stable installs
@@ -3603,6 +3594,15 @@ EOF
fi
fi
+if test "$fdt_required" = "yes"; then
+ if test "$fdt" = "no"; then
+ error_exit "fdt disabled but some requested targets require it." \
+ "You can turn off fdt only if you also disable all the system emulation" \
+ "targets which need it (by specifying a cut down --target-list)."
+ fi
+ fdt=yes
+fi
+
libs_softmmu="$libs_softmmu $fdt_libs"
##########################################
--
2.13.3
next prev parent reply other threads:[~2017-07-26 21:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-26 21:40 [Qemu-devel] [PATCH for 2.10 0/4] check dtc submodule is outdated Philippe Mathieu-Daudé
2017-07-26 21:40 ` [Qemu-devel] [PATCH 1/4] configure: remember the user to run 'git submodule' command in source dir Philippe Mathieu-Daudé
2017-07-26 21:51 ` Eric Blake
2017-07-26 22:02 ` Philippe Mathieu-Daudé
2017-07-26 21:40 ` Philippe Mathieu-Daudé [this message]
2017-07-26 21:53 ` [Qemu-devel] [PATCH for 2.10 2/4] fdt: check fdt_required condition can be satisfied _after_ testing libfdt Eric Blake
2017-07-27 21:46 ` Michael Roth
2017-07-26 21:40 ` [Qemu-devel] [PATCH for 2.10 3/4] fdt: probe for v1.4.2 using fdt_setprop_inplace_namelen_partial() Philippe Mathieu-Daudé
2017-07-27 21:43 ` Michael Roth
2017-07-27 22:45 ` Michael Roth
2017-07-26 21:40 ` [Qemu-devel] [RFC PATCH for 2.10 4/4] fdt: compile dtc submodule to check it is up-to-date Philippe Mathieu-Daudé
2017-07-26 21:47 ` [Qemu-devel] [PATCH for 2.10 0/4] check dtc submodule is outdated no-reply
2017-07-26 21:56 ` Eric Blake
2017-07-26 22:05 ` Philippe Mathieu-Daudé
2017-07-27 4:39 ` 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=20170726214010.420-3-f4bug@amsat.org \
--to=f4bug@amsat.org \
--cc=aurelien@aurel32.net \
--cc=crosthwaite.peter@gmail.com \
--cc=james.hogan@imgtec.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=programmingkidx@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=yongbok.kim@imgtec.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).