From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] automake: update gtk-doc.m4 to serial 2
Date: Fri, 10 Oct 2014 12:41:01 +0200 [thread overview]
Message-ID: <20141010124101.0388b2b3@free-electrons.com> (raw)
In-Reply-To: <1412936897-8478-1-git-send-email-gustavo@zacarias.com.ar>
Dear Gustavo Zacarias,
On Fri, 10 Oct 2014 07:28:16 -0300, Gustavo Zacarias wrote:
> -HOST_AUTOMAKE_DEPENDENCIES = host-autoconf
> +HOST_AUTOMAKE_DEPENDENCIES = host-autoconf host-pkgconf
I'm not sure exactly, but shouldn't depending on host-pkgconf be the
responsibility of each individual package that uses the gtk-doc.m4
stuff?
Even though I agree pkgconf is fairly quick to build, I find it odd to
have host-automake depend on host-pkgconf if it's only a very limited
number of packages that actually use the gtk-doc.m4 stuff that need the
host-pkgconf dependency.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-10-10 10:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-10 10:28 [Buildroot] [PATCH 1/2] automake: update gtk-doc.m4 to serial 2 Gustavo Zacarias
2014-10-10 10:28 ` [Buildroot] [PATCH 2/2] kmod: needs to autoreconf Gustavo Zacarias
2014-10-10 10:36 ` Vicente Olivert Riera
2014-10-12 9:07 ` Peter Korsgaard
2014-10-10 10:35 ` [Buildroot] [PATCH 1/2] automake: update gtk-doc.m4 to serial 2 Vicente Olivert Riera
2014-10-10 10:41 ` Thomas Petazzoni [this message]
2014-10-10 10:45 ` Gustavo Zacarias
2014-10-10 11:01 ` Thomas Petazzoni
2014-10-10 11:12 ` Gustavo Zacarias
2014-10-10 13:28 ` Thomas Petazzoni
2014-10-10 13:50 ` Gustavo Zacarias
2014-10-12 9:07 ` Peter Korsgaard
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=20141010124101.0388b2b3@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.