From: Thomas Huth <thuth@redhat.com>
To: "Philippe Mathieu-Daudé" <f4bug@amsat.org>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Stefan Hajnoczi" <stefanha@redhat.com>,
"Eric Blake" <eblake@redhat.com>,
"Michael Tokarev" <mjt@tls.msk.ru>
Cc: qemu-devel@nongnu.org, "Daniel P. Berrangé" <berrange@redhat.com>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>,
"YunQiang Su" <syq@debian.org>,
"David Gibson" <david@gibson.dropbear.id.au>
Subject: Re: [Qemu-devel] [PATCH 2/4] configure: Display if libfdt is from system or git
Date: Mon, 16 Apr 2018 07:16:38 +0200 [thread overview]
Message-ID: <5adfa8ce-b400-b017-5495-a0690decd183@redhat.com> (raw)
In-Reply-To: <20180415230522.24404-3-f4bug@amsat.org>
On 16.04.2018 01:05, Philippe Mathieu-Daudé wrote:
> The configure script outputs "yes" regardless which libfdt is used:
>
> ./configure
> [...]
> fdt support yes
>
> Sometimes you can have both system and local git version available,
> change the configure script to display which library got selected:
>
> debian8$ dpkg-query --showformat='${Version}\n' --show libfdt-dev
> 1.4.0+dfsg-1
>
> debian8$ ./configure
> [...]
> fdt support git
>
> Signed-off-by: Philippe Mathieu-Daudé <f4bug@amsat.org>
> ---
> configure | 9 ++++-----
> 1 file changed, 4 insertions(+), 5 deletions(-)
>
> diff --git a/configure b/configure
> index 162e804b49..056b391f22 100755
> --- a/configure
> +++ b/configure
> @@ -3758,15 +3758,14 @@ int main(void) { fdt_first_subnode(0, 0); return 0; }
> EOF
> if compile_prog "" "$fdt_libs" ; then
> # system DTC is good - use it
> - fdt=yes
> + fdt=system
> else
> # have GIT checkout, so activate dtc submodule
> if test -e "${source_path}/.git" ; then
> git_submodules="${git_submodules} dtc"
> fi
> if test -d "${source_path}/dtc/libfdt" || test -e "${source_path}/.git" ; then
> - fdt=yes
> - dtc_internal="yes"
> + fdt=git
That's ok for git checkout, but what about release tarballs? I'd strange
to see "git" here. So maybe better use "internal" instead of "git" here?
OTOH, capstone is also using the term "git" here, so this is just
consistent here...
Thomas
next prev parent reply other threads:[~2018-04-16 5:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-15 23:05 [Qemu-devel] [PATCH 0/4] build: fix failure when host provides too old libfdt Philippe Mathieu-Daudé
2018-04-15 23:05 ` [Qemu-devel] [PATCH for-2.12? 1/4] configure: Really use local libfdt if the system one is too old Philippe Mathieu-Daudé
2018-04-16 5:22 ` Thomas Huth
2018-04-15 23:05 ` [Qemu-devel] [PATCH 2/4] configure: Display if libfdt is from system or git Philippe Mathieu-Daudé
2018-04-16 5:16 ` Thomas Huth [this message]
2018-04-16 10:40 ` Philippe Mathieu-Daudé
2018-04-15 23:05 ` [Qemu-devel] [PATCH 3/4] shippable: Remove Debian 8 libfdt kludge Philippe Mathieu-Daudé
2018-04-15 23:05 ` [Qemu-devel] [PATCH 4/4] build: Silence dtc directory creation Philippe Mathieu-Daudé
2018-05-07 17:03 ` [Qemu-devel] [PATCH 0/4] build: fix failure when host provides too old libfdt Paolo Bonzini
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=5adfa8ce-b400-b017-5495-a0690decd183@redhat.com \
--to=thuth@redhat.com \
--cc=berrange@redhat.com \
--cc=david@gibson.dropbear.id.au \
--cc=eblake@redhat.com \
--cc=f4bug@amsat.org \
--cc=marcandre.lureau@redhat.com \
--cc=mjt@tls.msk.ru \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=syq@debian.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).