Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 3/3] lttng-tools: bump to version 2.10.1
Date: Tue, 21 Nov 2017 09:13:33 +0100	[thread overview]
Message-ID: <20171121091333.6213c754@windsurf.lan> (raw)
In-Reply-To: <20171120232006.22588-3-eeppeliteloop@gmail.com>

Hello,

On Mon, 20 Nov 2017 18:20:06 -0500, Philippe Proulx wrote:
> Adding 0001-Fix-detect-dlmopen-and-disable-corresponding-tests-i.patch
> to detect if dlmopen() exists and disable parts of the build accordingly
> if not. This fixes a bug when building with musl or uClibc-ng.
> 
> Adding 0002-Fix-src-common-pipe.h-include-sys-types.h-for-ssize_.patch
> to fix an #include bug when building with musl.
> 
> Adding 0003-Fix-warning-src-bin-lttng-utils.c-cast-incompatible-.patch
> to remove compilation warnings.
> 
> All three new patches are in upstream's master branch as of this date
> and will be part of an eventual release.
> 
> Signed-off-by: Philippe Proulx <eeppeliteloop@gmail.com>

Thanks for working on this!

> diff --git a/package/lttng-tools/0001-Fix-detect-dlmopen-and-disable-corresponding-tests-i.patch b/package/lttng-tools/0001-Fix-detect-dlmopen-and-disable-corresponding-tests-i.patch
> new file mode 100644
> index 0000000000..8e14a14413
> --- /dev/null
> +++ b/package/lttng-tools/0001-Fix-detect-dlmopen-and-disable-corresponding-tests-i.patch
> @@ -0,0 +1,249 @@
> +From bc1d8ca01415710d40224de312c7ecf6f4223301 Mon Sep 17 00:00:00 2001
> +From: Philippe Proulx <eeppeliteloop@gmail.com>
> +Date: Mon, 6 Nov 2017 18:46:41 -0500
> +Subject: [PATCH] Fix: detect dlmopen() and disable corresponding tests if not
> + available
> +MIME-Version: 1.0
> +Content-Type: text/plain; charset=UTF-8
> +Content-Transfer-Encoding: 8bit
> +
> +musl and uClibc-ng are known not to support dlmopen(). LTTng-UST has
> +this dlmopen() detection.
> +
> +Signed-off-by: Philippe Proulx <eeppeliteloop@gmail.com>
> +[Philippe: backport from upstream commit bc1d8ca0
> +           edited to remove .gitignore part]
> +Signed-off-by: J?r?mie Galarneau <jeremie.galarneau@efficios.com>

Would it be possible to get just this patch, on the current version of
lttng-tools.

Indeed, we want to fix the build issue of lttng-tools in Buildroot's
master branch, but the version bumps can only got in the next branch.

Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

  reply	other threads:[~2017-11-21  8:13 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-20 23:20 [Buildroot] [PATCH 1/3] lttng-modules: bump version to 2.10.4 Philippe Proulx
2017-11-20 23:20 ` [Buildroot] [PATCH 2/3] lttng-libust: bump version to 2.10.0 Philippe Proulx
2017-11-21 19:04   ` [Buildroot] [2/3] " Trent Piepho
2017-11-21 19:06     ` Philippe Proulx
2017-11-21 19:15       ` Trent Piepho
2017-11-20 23:20 ` [Buildroot] [PATCH 3/3] lttng-tools: bump to version 2.10.1 Philippe Proulx
2017-11-21  8:13   ` Thomas Petazzoni [this message]
  -- strict thread matches above, loose matches on Subject: below --
2017-11-22 22:55 [Buildroot] [PATCH 1/3] lttng-modules: bump version to 2.10.4 Philippe Proulx
2017-11-22 22:55 ` [Buildroot] [PATCH 3/3] lttng-tools: bump to version 2.10.1 Philippe Proulx

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=20171121091333.6213c754@windsurf.lan \
    --to=thomas.petazzoni@free-electrons.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox