From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/eudev: fix build with gperf 3.1
Date: Sun, 22 Jan 2017 17:47:16 +1100 [thread overview]
Message-ID: <20170122174716.143b256b@free-electrons.com> (raw)
In-Reply-To: <20170121200112.12593-1-bernd.kuhls@t-online.de>
Hello,
On Sat, 21 Jan 2017 21:01:12 +0100, Bernd Kuhls wrote:
> Fixes
> http://autobuild.buildroot.net/results/1a0/1a0e76e2782a63e2b2fc2fc0d79471802afa4d35/
>
> Tested on current buildroot master (eb6bb3411) with and without
> http://patchwork.ozlabs.org/patch/716134/
>
> Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de>
Since we have reverted the bump to gperf 3.1, I'm not sure it makes
sense to add a patch to fix an issue that doesn't exist.
An e-mail has been sent to the gperf maintainers to let them know that
version 3.1 breaks backward compatibility. We probably should wait for
their feedback before adding more stuff to Buildroot.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
prev parent reply other threads:[~2017-01-22 6:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-21 20:01 [Buildroot] [PATCH 1/1] package/eudev: fix build with gperf 3.1 Bernd Kuhls
2017-01-22 6:47 ` 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=20170122174716.143b256b@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