All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] automake: update gtk-doc.m4 to serial 2
Date: Fri, 10 Oct 2014 07:45:07 -0300	[thread overview]
Message-ID: <5437B8B3.7070105@zacarias.com.ar> (raw)
In-Reply-To: <20141010124101.0388b2b3@free-electrons.com>

On 10/10/2014 07:41 AM, Thomas Petazzoni wrote:

> 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.

The problem is it wasn't the case for gtk-doc.m4 serial 1, the check and
need for pkgconfig is done after gtk-doc is enabled, but for serial 2
some of the checks are done before that.
So we'd need to find all packages that use gtk-doc.m4 and add it there
(well, for those that autoreconf, but that would be sloppy since an
added autoreconf would trigger the need).
As stated i prefer to keep it simple without patching gtk-doc.m4 for
when serial 3 comes around.
Regards.

  reply	other threads:[~2014-10-10 10:45 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
2014-10-10 10:45   ` Gustavo Zacarias [this message]
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=5437B8B3.7070105@zacarias.com.ar \
    --to=gustavo@zacarias.com.ar \
    --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.