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 next 4/4] fontconfig: add build fix for glibc 2.25
Date: Wed, 1 Mar 2017 23:39:36 +0100	[thread overview]
Message-ID: <20170301233936.0ed3f6c2@free-electrons.com> (raw)
In-Reply-To: <20170225003448.32459-4-gustavo@zacarias.com.ar>

Hello,

On Fri, 24 Feb 2017 21:34:48 -0300, Gustavo Zacarias wrote:
> Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar>
> ---
>  ...ts-with-integer-width-macros-from-TS-1866.patch | 50 ++++++++++++++++++++++
>  1 file changed, 50 insertions(+)
>  create mode 100644 package/fontconfig/0001-Avoid-conflicts-with-integer-width-macros-from-TS-1866.patch

This seems to break the build of fontconfig, because it causes a file
generated by gperf to be regenerated, or something like that:

  http://autobuild.buildroot.net/results/fcd/fcd27645f47f28b989bebfec2d65f5fdb72329c6/build-end.log
  http://autobuild.buildroot.net/results/054/054b56978bd75980658fecb44d46416fa60ac98b/build-end.log

Could you have a look?

Thanks,

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

  reply	other threads:[~2017-03-01 22:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-25  0:34 [Buildroot] [PATCH next 1/4] glibc: bump default to version 2.24 Gustavo Zacarias
2017-02-25  0:34 ` [Buildroot] [PATCH next 2/4] glibc: add version 2.25 Gustavo Zacarias
2017-02-25  0:34 ` [Buildroot] [PATCH next 3/4] glibc: drop version 2.22 Gustavo Zacarias
2017-02-25  0:34 ` [Buildroot] [PATCH next 4/4] fontconfig: add build fix for glibc 2.25 Gustavo Zacarias
2017-03-01 22:39   ` Thomas Petazzoni [this message]
2017-03-01 21:46 ` [Buildroot] [PATCH next 1/4] glibc: bump default to version 2.24 Thomas Petazzoni

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=20170301233936.0ed3f6c2@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