From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Alexander Kanavin <alexander.kanavin@linux.intel.com>,
"Burton, Ross" <ross.burton@intel.com>,
Khem Raj <raj.khem@gmail.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 05/11] gperf: upgrade to 3.1
Date: Mon, 31 Jul 2017 10:43:37 +0100 [thread overview]
Message-ID: <1501494217.18633.0.camel@linuxfoundation.org> (raw)
In-Reply-To: <287709d4-1010-10fa-fd94-929e4c465e49@linux.intel.com>
On Mon, 2017-07-31 at 12:35 +0300, Alexander Kanavin wrote:
> On 07/28/2017 05:50 PM, Burton, Ross wrote:
> >
> > And libid3tag:
> >
> > >
> > > compat.gperf:116:1: error: conflicting types for
> > > 'id3_compat_lookup' |
> > In file included from compat.gperf:37:0: |
> > ../libid3tag-0.15.1b/compat.h:36:26: note: previous declaration of
> > 'id3_compat_lookup' was here | struct id3_compat const
> > *id3_compat_lookup(register char const *, | ^~~~~~~~~~~~~~~~~
> >
> > http://git.savannah.gnu.org/cgit/gperf.git/commit/?id=d519d1a821511
> > eaa22eae6d9019a548aea21e6d3
> > is the upstream commit that breaks everything, because the API of
> > the
> > generated files has changed.
> Right. Should we just stop fighting with this, and put a
> RECIPE_NO_UPDATE_REASON into gperf? I'd rather not update gperf with
> this change reverted.
It does feel like upstream screwed up and should really sort this out.
Do you know what upstream plan to do (if anything)?
Cheers,
Richard
next prev parent reply other threads:[~2017-07-31 9:43 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-24 14:28 [PATCH 01/11] icu: update to 59.1 Alexander Kanavin
2017-07-24 14:28 ` [PATCH 02/11] btrfs-tools: upgrade to 4.11.1 Alexander Kanavin
2017-07-24 14:28 ` [PATCH 03/11] bash-completion: upgrade to 2.7 Alexander Kanavin
2017-07-24 14:28 ` [PATCH 04/11] epiphany: upgrade to 3.24.3 Alexander Kanavin
2017-07-24 14:28 ` [PATCH 05/11] gperf: upgrade to 3.1 Alexander Kanavin
2017-07-25 13:12 ` Burton, Ross
2017-07-25 13:53 ` Khem Raj
2017-07-28 14:50 ` Burton, Ross
2017-07-31 9:35 ` Alexander Kanavin
2017-07-31 9:43 ` Richard Purdie [this message]
2017-07-31 9:53 ` Alexander Kanavin
2017-07-31 10:18 ` Alexander Kanavin
2017-07-31 14:55 ` Burton, Ross
2017-07-31 14:58 ` Khem Raj
2017-07-31 15:03 ` Burton, Ross
2017-07-24 14:28 ` [PATCH 06/11] vala: upgrade to 0.36.4 Alexander Kanavin
2017-07-24 14:28 ` [PATCH 07/11] eudev: update to 3.2.2 Alexander Kanavin
2017-07-24 14:28 ` [PATCH 08/11] mpg123: update to 1.25.4 Alexander Kanavin
2017-07-24 14:28 ` [PATCH 09/11] oprofile: fix upstream version check Alexander Kanavin
2017-07-24 14:28 ` [PATCH 10/11] webkitgtk: update to 2.16.6 Alexander Kanavin
2017-07-24 14:28 ` [PATCH 11/11] valgrind: fix upstream version check Alexander Kanavin
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=1501494217.18633.0.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=alexander.kanavin@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.com \
--cc=ross.burton@intel.com \
/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