From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Alexey Kardashevskiy <aik@ozlabs.ru>
Cc: qemu-devel@nongnu.org, qemu-ppc@nongnu.org,
David Gibson <david@gibson.dropbear.id.au>,
Greg Kurz <groug@kaod.org>
Subject: Re: [Qemu-devel] [PATCH qemu 1/3] configure/fdt: Use more strict test for libfdt version
Date: Tue, 11 Dec 2018 09:31:58 +0000 [thread overview]
Message-ID: <20181211093158.GB921@redhat.com> (raw)
In-Reply-To: <20181211054926.56717-2-aik@ozlabs.ru>
On Tue, Dec 11, 2018 at 04:49:24PM +1100, Alexey Kardashevskiy wrote:
> The libfdt installed in the system is preferred to the dtc submodule by
> default. The recent libfdt update added a new symbol - fdt_check_full -
> and this breaks compile if there is an older libfdt installed in
> the system.
AFACT, there's no usage of fdt_check_full in the QMEU tree, so this
commit message is wrong. The first usage is introduced in your
next patch, so this configure change should just be part of that
patch which introduces it.
>
> This changes the test to force ./configure into using newer libfdt.
>
> Signed-off-by: Alexey Kardashevskiy <aik@ozlabs.ru>
> ---
> configure | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/configure b/configure
> index 0a3c6a7..e5312da 100755
> --- a/configure
> +++ b/configure
> @@ -3880,7 +3880,7 @@ if test "$fdt" != "no" ; then
> cat > $TMPC << EOF
> #include <libfdt.h>
> #include <libfdt_env.h>
> -int main(void) { fdt_first_subnode(0, 0); return 0; }
> +int main(void) { fdt_check_full(NULL, 0); return 0; }
> EOF
> if compile_prog "" "$fdt_libs" ; then
> # system DTC is good - use it
> --
> 2.17.1
>
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2018-12-11 9:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-11 5:49 [Qemu-devel] [PATCH qemu 0/3] ppc/spapr: Receive and store device tree blob from SLOF Alexey Kardashevskiy
2018-12-11 5:49 ` [Qemu-devel] [PATCH qemu 1/3] configure/fdt: Use more strict test for libfdt version Alexey Kardashevskiy
2018-12-11 9:31 ` Daniel P. Berrangé [this message]
2018-12-11 16:16 ` [Qemu-devel] [Qemu-ppc] " Greg Kurz
2018-12-11 5:49 ` [Qemu-devel] [PATCH qemu 2/3] ppc/spapr: Receive and store device tree blob from SLOF Alexey Kardashevskiy
2018-12-11 16:35 ` [Qemu-devel] [Qemu-ppc] " Greg Kurz
2018-12-11 23:57 ` Alexey Kardashevskiy
2018-12-12 9:46 ` Greg Kurz
2018-12-13 2:53 ` Alexey Kardashevskiy
2018-12-13 7:59 ` Greg Kurz
2018-12-11 5:49 ` [Qemu-devel] [PATCH qemu 3/3] spapr: Fix fdt warnings Alexey Kardashevskiy
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=20181211093158.GB921@redhat.com \
--to=berrange@redhat.com \
--cc=aik@ozlabs.ru \
--cc=david@gibson.dropbear.id.au \
--cc=groug@kaod.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@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).