From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH/next 1/1] package/fontconfig: bump version to 2.12.4
Date: Sat, 2 Sep 2017 19:06:28 +0200 [thread overview]
Message-ID: <20170902190628.462af963@windsurf.lan> (raw)
In-Reply-To: <20170806073155.18409-1-bernd.kuhls@t-online.de>
Hello,
On Sun, 6 Aug 2017 09:31:55 +0200, Bernd Kuhls wrote:
> Removed patch applied upstream:
> https://cgit.freedesktop.org/fontconfig/commit/?id=1ab5258f7c2abfafcd63a760ca08bf93591912da
>
> Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de>
This commit broke the build, because the host-gperf dependency is still
necessary. I hadn't noticed it used to be there, so I simply reverted.
I think it's weird for fontconfig to need host-gperf, as it already
ships the generated files: but the dependencies in the Makefile.am look
bogus to me.
So, can we have a bump to 2.12.4 that keeps the host-gperf dependency,
*and* a bug report submitted upstream about this host-gperf dependency ?
I think rules like:
fcobjshash.gperf: Makefile stamp-fcobjshash.gperf
and:
fcobjshash.h: Makefile fcobjshash.gperf
are bogus, because the configure script generates the Makefile. So the
Makefile is always going to be newer than the shipped fcobjshash.h and
fcobjhash.gperf, and those will always be re-generated.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-09-02 17:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-06 7:31 [Buildroot] [PATCH/next 1/1] package/fontconfig: bump version to 2.12.4 Bernd Kuhls
2017-09-02 17:06 ` Thomas Petazzoni [this message]
2017-09-02 17:32 ` Bernd Kuhls
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=20170902190628.462af963@windsurf.lan \
--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