All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] bluez-utils: disable on avr32
Date: Tue, 13 Nov 2012 21:22:11 +0100	[thread overview]
Message-ID: <50A2ABF3.9050206@mind.be> (raw)
In-Reply-To: <1352797007-9509-1-git-send-email-spdawson@gmail.com>

On 13/11/12 09:56, spdawson at gmail.com wrote:
> From: Simon Dawson<spdawson@gmail.com>
>
> The bluez-utils package does not build for the avr32 architecture; this
> results in autobuilder failures such as the following.
>
>    http://autobuild.buildroot.net/results/d737d1220d7566289eee802fd580a49d8c456c97/build-end.log
>
> The underlying problem is with the<sys/epoll.h>  header provided by the
> antiquated avr32 toolchain; this header lacks definitions for
> epoll_create1() and EPOLL_CLOEXEC.
>
> This patch disables support for the bluez-utils package on the avr32
> architecture.
>
> Signed-off-by: Simon Dawson<spdawson@gmail.com>

Acked-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>

This one is for 2012.11.

  Regards,
  Arnout
-- 
Arnout Vandecappelle                               arnout at mind be
Senior Embedded Software Architect                 +32-16-286540
Essensium/Mind                                     http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium                BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F

  reply	other threads:[~2012-11-13 20:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-13  8:56 [Buildroot] [PATCH v2] bluez-utils: disable on avr32 spdawson at gmail.com
2012-11-13 20:22 ` Arnout Vandecappelle [this message]
2012-11-14 21:30 ` 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=50A2ABF3.9050206@mind.be \
    --to=arnout@mind.be \
    --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.