All of lore.kernel.org
 help / color / mirror / Atom feed
From: Romain NAOUR <romain.naour@smile.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/libcap: fix build with gperf >= 3.1
Date: Wed, 18 Jan 2017 11:43:28 +0100	[thread overview]
Message-ID: <aeece1d0a3287c8df1f4d538826706fd@smile.fr> (raw)
In-Reply-To: <87r340u0b8.fsf@dell.be.48ers.dk>

Hi Peter,

Le 2017-01-18 11:31, Peter Korsgaard a ?crit :

>>>>>> "Romain" == Romain Naour <romain.naour@gmail.com> writes:
> 
>> See gperf 3.1 ChangeLog:
>> * The 'len' parameter of the hash function and of the lookup function
> is now
>> of type 'size_t' instead of 'unsigned int'. This makes it safe to 
>> call
> these
>> functions with strings of length > 4 GB, on 64-bit machines.
> 
> :/
> 
> Have you submitted this patch upstream? Doesn't this then break 
> building
> against gperf <3.1?

Not yet. Indeed it break with gperf < 3.1 :-/
But I don't see how we can easily/properly handle the gperf version 
checking
in the libcap Makefile...

> 
> I think I'll apply Gustavoz patch to (temporarily) revert the gperf 
> bump
> instead. Once we have sorted out this libcap issue (and apparently 
> eudev
> as well) we can bump the version again.

Ok, it will give some time to Alvaro for investigation and test.

Best regards,
Romain

  reply	other threads:[~2017-01-18 10:43 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-17 22:17 [Buildroot] [PATCH] package/libcap: fix build with gperf >= 3.1 Romain Naour
2017-01-18  6:13 ` Alvaro Gamez
2017-01-18 10:31 ` Peter Korsgaard
2017-01-18 10:43   ` Romain NAOUR [this message]
2017-01-18 10:37 ` Thomas Petazzoni
2017-01-18 10:50   ` Romain NAOUR
2017-01-18 11:22 ` Alvaro G. M.
2017-01-18 16:01   ` Alvaro G. M.
2017-01-18 21:31     ` Romain Naour
2017-01-19 10:07       ` Alvaro G. M.

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=aeece1d0a3287c8df1f4d538826706fd@smile.fr \
    --to=romain.naour@smile.fr \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.