From: David Gibson <david@gibson.dropbear.id.au>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Peter Crosthwaite <peter.crosthwaite@xilinx.com>,
qemu-devel@nongnu.org, edgar.iglesias@gmail.com
Subject: Re: [Qemu-devel] [PATCH v2 1/1] configure: dtc: Probe for libfdt_env.h
Date: Sat, 1 Jun 2013 15:38:33 +1000 [thread overview]
Message-ID: <20130601053833.GC12059@boomeroo.fritz.box> (raw)
In-Reply-To: <CAFEAcA91DYpsh2k0-C8uhwRtaouyAhvinsKF3qrjLcehvYeGag@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1643 bytes --]
On Fri, May 31, 2013 at 10:44:33AM +0100, Peter Maydell wrote:
> On 31 May 2013 09:25, Paolo Bonzini <pbonzini@redhat.com> wrote:
> > Please don't. Fedora is not going to use the bundled dtc because of a
> > policy against bundling, and Fedora's dtc package doesn't include
> > libfdt_env.h.
>
> It sounds like Fedora's dtc package is broken then -- are you
> going to fix it?
>
> > If David says that the changes are rare enough, let's just fix the
> > bundled libfdt_env.h.
>
> ...I don't have an objection to this if we can make it
> work for all versions of libfdt, and if it's a way of
> using libfdt that upstream expects and is happy to support.
>
> Mostly I'd just like it to be clear how upstream expects us
> to use libfdt and how upstream expects distributions to
> package libfdt, and then make sure we're in line with that.
> It seems like a lot of the problem is that people (us and
> distros) have been guessing in the absence of documentation :-(
Yeah. Sorry. Patches welcome..?
The key point of confusion here is that it is the *builder* of libfdt
that's expected to provide libfdt_env.h, not the user. So if you're
pulling in a prebuilt libfdt from elsewhere, you should be pulling in
libfdt_env.h from the same elsewhere.
So, a distro packaging libfdt must provide the libfdt_env.h it built
with - which in this case I'd expect to be the standard/default
version from the libfdt tree.
--
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: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2013-06-01 5:45 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-27 4:20 [Qemu-devel] [PATCH v2 1/1] configure: dtc: Probe for libfdt_env.h peter.crosthwaite
2013-05-29 8:18 ` David Gibson
2013-05-29 9:14 ` Peter Maydell
2013-05-29 9:31 ` David Gibson
2013-05-31 1:48 ` Peter Crosthwaite
2013-05-31 3:32 ` David Gibson
2013-05-31 8:25 ` Paolo Bonzini
2013-05-31 9:44 ` Peter Maydell
2013-05-31 9:54 ` Paolo Bonzini
2013-05-31 12:37 ` Peter Crosthwaite
2013-06-01 5:38 ` David Gibson [this message]
2013-06-01 23:13 ` Peter Crosthwaite
2013-06-07 2:54 ` Peter Crosthwaite
2013-06-07 8:32 ` Peter Maydell
2013-06-01 5:22 ` David Gibson
2013-06-01 8:26 ` Peter Maydell
2013-06-01 23:09 ` Peter Crosthwaite
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=20130601053833.GC12059@boomeroo.fritz.box \
--to=david@gibson.dropbear.id.au \
--cc=edgar.iglesias@gmail.com \
--cc=pbonzini@redhat.com \
--cc=peter.crosthwaite@xilinx.com \
--cc=peter.maydell@linaro.org \
--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).