From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3] package/sysdig: bump to version 0.22.1
Date: Fri, 10 Aug 2018 13:57:55 +0200 [thread overview]
Message-ID: <20180810135755.121222b8@windsurf> (raw)
In-Reply-To: <1533888631-7613-1-git-send-email-angelo@amarulasolutions.com>
Hello,
On Fri, 10 Aug 2018 10:10:31 +0200, Angelo Compagnucci wrote:
> This patch bumps sysdig to version 0.22.1, adds a new dependency on
> elfutils and adds hash for the license file.
>
> Signed-off-by: Angelo Compagnucci <angelo@amarulasolutions.com>
> ---
> package/sysdig/Config.in | 5 ++++-
> package/sysdig/sysdig.hash | 5 +++--
> package/sysdig/sysdig.mk | 4 ++--
> 3 files changed, 9 insertions(+), 5 deletions(-)
>
> diff --git a/package/sysdig/Config.in b/package/sysdig/Config.in
> index 6ccb706..f87b5dd 100644
> --- a/package/sysdig/Config.in
> +++ b/package/sysdig/Config.in
> @@ -4,7 +4,9 @@ config BR2_PACKAGE_SYSDIG
> depends on BR2_INSTALL_LIBSTDCPP # libjson
> depends on BR2_PACKAGE_LUAJIT_ARCH_SUPPORTS
> depends on BR2_TOOLCHAIN_GCC_AT_LEAST_4_8
> - depends on !BR2_STATIC_LIBS # luajit
> + depends on !BR2_STATIC_LIBS # luajit, elfutils
> + depends on BR2_USE_WCHAR # elfutils
> + depends on BR2_TOOLCHAIN_USES_UCLIBC || BR2_TOOLCHAIN_USES_GLIBC # elfutils
When you add dependencies, the Config.in comment mentioning the
dependencies should be updated as well.
Thomas
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2018-08-10 11:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-10 8:10 [Buildroot] [PATCH v3] package/sysdig: bump to version 0.22.1 Angelo Compagnucci
2018-08-10 11:57 ` 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=20180810135755.121222b8@windsurf \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox