Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] fontconfig: needs host-gperf
Date: Thu, 2 Mar 2017 09:25:53 +0100	[thread overview]
Message-ID: <20170302092553.67502cda@free-electrons.com> (raw)
In-Reply-To: <1488440033-18982-1-git-send-email-rahul.bedarkar@imgtec.com>

Hello,

On Thu, 2 Mar 2017 13:03:53 +0530, Rahul Bedarkar wrote:
> Commit 701380c53b4d("fontconfig: add build fix for glibc 2.25") added
> a patch that touches src/fcobjs.h. Package build system detects change
> in timestamp and tries to regenerate fcobjshash.gperf which requires
> gperf tool. So this commit adds dependency on host-gperf.
> 
> Since the patch is in upstream fontconfig, we can get rid of this
> dependency once version is bumped next time.
> 
> Fixes:
>   http://autobuild.buildroot.net/results/174/17471088b26ebc840d1922d7f2aa9e69b4b49ced
> 
> Cc: Gustavo Zacarias <gustavo@zacarias.com.ar>
> Signed-off-by: Rahul Bedarkar <rahul.bedarkar@imgtec.com>

I've applied to master, with one little change, see below.

> +# When bumping version next time, we can get rid of dependency on host-gperf

Rather than talking about "bumping version next time", I changed this
to "When patch ... is removed, the host-gperf dependency should be
removed".

Peter: this does not need to go to the LTS branch.

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

      reply	other threads:[~2017-03-02  8:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-02  7:33 [Buildroot] [PATCH] fontconfig: needs host-gperf Rahul Bedarkar
2017-03-02  8:25 ` Thomas Petazzoni [this message]

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=20170302092553.67502cda@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox