From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] fontconfig: bump to version 2.8.0
Date: Fri, 14 Jan 2011 09:28:50 +0100 [thread overview]
Message-ID: <20110114092850.1fb27fc1@surf> (raw)
In-Reply-To: <BAY145-w55783B9ED56A589ABC3816C2F30@phx.gbl>
Matt,
On Thu, 13 Jan 2011 21:12:09 -0700
Matt Johnson <mj1856@hotmail.com> wrote:
> Signed-off-by: Matt Johnson <mj1856@hotmail.com>
> ---
> ...fontconfig-2.6.0-parallel-compilation-fix.patch | 26 -------
In the commit description, would be great to say that the
parallel-compilation-fix patch is no longer necessary since it has been
merged upstream at
http://cgit.freedesktop.org/fontconfig/commit/?id=0e21b5a4d5609a5dd0f332b412d878b6f1037d29
so that people reviewing your patch can easily understand why it's no
longer necessary.
> .../fontconfig-2.6.0-use_for_build.patch | 80 --------------------
> .../fontconfig-2.8.0-use_for_build.patch | 80 ++++++++++++++++++++
A patch has been committed upstream that intends to fix some
cross-compilation issues:
http://cgit.freedesktop.org/fontconfig/commit/?id=2a6b235ff6d2750171e8dff7cfdfe3bccb0f630e
but it is not part of fontconfig-2.8.0. Does it solve all problems
fixed by the use_for_build patch ? If so, I'd prefer to see an already
upstreamed patch used in Buildroot, with the proper comment mentionning
that the next version of fontconfig will include this fix.
Thanks!
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2011-01-14 8:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-14 4:12 [Buildroot] fontconfig: bump to version 2.8.0 Matt Johnson
2011-01-14 8:28 ` Thomas Petazzoni [this message]
2011-01-14 16:19 ` Matt Johnson
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=20110114092850.1fb27fc1@surf \
--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