On 07/31/2017 12:43 PM, Richard Purdie wrote:
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)?
The only thing I found was this email:
http://lists.gnu.org/archive/html/bug-gperf/2017-01/msg00004.html
which was ignored by upstream.
However, both debian testing and fedora rawhide have gperf 3.1, so I'm
not sure how they made it work. I'm running debian here, so can look
into this.
Alex
--
_______________________________________________
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
