All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vicente Olivert Riera <Vincent.Riera@imgtec.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] libev: don't install event.h
Date: Tue, 26 Aug 2014 12:51:43 +0100	[thread overview]
Message-ID: <53FC74CF.5050608@imgtec.com> (raw)
In-Reply-To: <1409052977-12935-1-git-send-email-gustavo@zacarias.com.ar>

On 08/26/2014 12:36 PM, Gustavo Zacarias wrote:
> It's a 'compatibility layer' with libevent which we:
> 1) Don't need
> 2) Possibly outdated with respect to libevent2
> 3) Causes build failures
>
> Fixes:
> http://autobuild.buildroot.net/results/451/4510fe02ef3497803ed27bf339dca07b3b073c10/
>
> Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar>
> ---
>   package/libev/libev.mk | 7 +++++++
>   1 file changed, 7 insertions(+)
>
> diff --git a/package/libev/libev.mk b/package/libev/libev.mk
> index a6ff3a9..dc42858 100644
> --- a/package/libev/libev.mk
> +++ b/package/libev/libev.mk
> @@ -10,4 +10,11 @@ LIBEV_INSTALL_STAGING = YES
>   LIBEV_LICENSE = BSD-2c or GPLv2+
>   LIBEV_LICENSE_FILES = LICENSE
>
> +# The 'compatibility' event.h header conflicts with libevent
> +# It's completely unnecessary for BR packages so remove it
> +define LIBEV_DISABLE_EVENT_H_INSTALL
> +	$(SED) 's/ event.h//' $(@D)/Makefile.in
> +endef
> +LIBEV_POST_PATCH_HOOKS += LIBEV_DISABLE_EVENT_H_INSTALL
> +
>   $(eval $(autotools-package))
>

Tested-by: Vicente Olivert Riera <Vincent.Riera@imgtec.com>

-- 
Vincent

  reply	other threads:[~2014-08-26 11:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-26 11:36 [Buildroot] [PATCH] libev: don't install event.h Gustavo Zacarias
2014-08-26 11:51 ` Vicente Olivert Riera [this message]
2014-08-26 21:49 ` Peter Korsgaard

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=53FC74CF.5050608@imgtec.com \
    --to=vincent.riera@imgtec.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 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.