All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3 1/1] LIBLO : bump version to 0.29
Date: Mon, 12 Feb 2018 16:54:03 +0100	[thread overview]
Message-ID: <20180212165403.296e993c@windsurf.lan> (raw)
In-Reply-To: <1518438804-7961-1-git-send-email-alexbaldwinmusic@gmail.com>

Hello,

On Mon, 12 Feb 2018 13:33:24 +0100, Alex B wrote:
> From: Alex <alexbaldwinmusic@gmail.com>
> 
> Starting from version 0.28, C++ wrappers are provided as well. The configure
> script appropriately detects the availability of a C++ compiler so no Buildroot
> changes are needed for this.
> 
> Building fails with --enable-ipv6 so --disable-ipv6 is needed in CONF_OPTS.
> This is known by liblo developers and building without ipv6 support is recomennded.
> 
> werror is kept on, so disable this with --disable-werror.
> 
> Patch to fix werror about redirect from sys/poll.h to poll.h
> 
> Liblo use's atomics, some architectures need explicit linking with libatomic. Added
> link to reflect this.
> 
> Included hash for license files.
> 
> Signed-off-by: Alex Baldwin <alexbaldwinmusic@gmail.com>

The liblo package has already been merged in the 'next' branch. So if
you want to send fixes, please send a patch on top of the current
'next' branch, i.e an incremental patch on top of what has already been
merged.

Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
http://bootlin.com

      reply	other threads:[~2018-02-12 15:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-12 12:33 [Buildroot] [PATCH v3 1/1] LIBLO : bump version to 0.29 Alex B
2018-02-12 15:54 ` Thomas Petazzoni [this message]

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=20180212165403.296e993c@windsurf.lan \
    --to=thomas.petazzoni@bootlin.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.