qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: David Gibson <david@gibson.dropbear.id.au>
To: "Daniel P. Berrangé" <berrange@redhat.com>
Cc: Alexey Kardashevskiy <aik@ozlabs.ru>,
	qemu-devel@nongnu.org, qemu-ppc@nongnu.org
Subject: Re: [Qemu-devel] [PATCH qemu] configure/fdt: Use more strict test for libfdt version
Date: Thu, 15 Nov 2018 21:33:08 +1100	[thread overview]
Message-ID: <20181115103308.GI2547@umbus.fritz.box> (raw)
In-Reply-To: <20181115101112.GF10900@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 2035 bytes --]

On Thu, Nov 15, 2018 at 10:11:12AM +0000, Daniel P. Berrangé wrote:
> On Thu, Nov 15, 2018 at 02:56:59PM +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.
> 
> Unless I'm missing something, QEMU doesn't use the fdt_check_full symbol,
> so why would the lack of this symbol cause a compile failure. 
> 
> It should be fine if the dtc submodule contains a newer libfdt than the
> host system. As long as QEMU doesn't actually need any of the APIs in
> the newer libfdt we should be able to continue using the older system
> version if it is present.
> 
> Could you elaborate on what build problems you are having.
> 
> > This changes the test to force ./configure into using newer libfdt.
> 
> I'm not convinced we want todo that.

So I think the point here is that Alexey has some other outstanding
patches that will use fdt_check_full().  The commit message needs to
make that clear though.  Or else include this patch in that series.

> 
> > 
> > Signed-off-by: Alexey Kardashevskiy <aik@ozlabs.ru>
> > ---
> >  configure | 2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> > 
> > diff --git a/configure b/configure
> > index 74e313a..7e16a6c 100755
> > --- a/configure
> > +++ b/configure
> > @@ -3826,7 +3826,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
> 
> Regards,
> Daniel

-- 
David Gibson			| I'll have my music baroque, and my code
david AT gibson.dropbear.id.au	| minimalist, thank you.  NOT _the_ _other_
				| _way_ _around_!
http://www.ozlabs.org/~dgibson

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2018-11-15 10:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-15  3:56 [Qemu-devel] [PATCH qemu] configure/fdt: Use more strict test for libfdt version Alexey Kardashevskiy
2018-11-15 10:11 ` Daniel P. Berrangé
2018-11-15 10:33   ` David Gibson [this message]
2018-11-15 10:39     ` Daniel P. Berrangé

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=20181115103308.GI2547@umbus.fritz.box \
    --to=david@gibson.dropbear.id.au \
    --cc=aik@ozlabs.ru \
    --cc=berrange@redhat.com \
    --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).