All of lore.kernel.org
 help / color / mirror / Atom feed
From: Petr Vorel <petr.vorel@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/iputils: fix static build with gcrypt
Date: Sat, 8 Jun 2019 00:12:25 +0200	[thread overview]
Message-ID: <20190607221224.GA4673@x230> (raw)
In-Reply-To: <20190607214931.30262-1-fontaine.fabrice@gmail.com>

Hi,

> Fixes:
>  - http://autobuild.buildroot.net/results/fb698e3e903869978bd5e69d791ec362317b7981

> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
> ---
>  ...n.build-fix-static-build-with-gcrypt.patch | 55 +++++++++++++++++++
>  1 file changed, 55 insertions(+)
>  create mode 100644 package/iputils/0002-meson.build-fix-static-build-with-gcrypt.patch

> diff --git a/package/iputils/0002-meson.build-fix-static-build-with-gcrypt.patch b/package/iputils/0002-meson.build-fix-static-build-with-gcrypt.patch
> new file mode 100644
> index 0000000000..de58b7e03e
> --- /dev/null
> +++ b/package/iputils/0002-meson.build-fix-static-build-with-gcrypt.patch
> @@ -0,0 +1,55 @@
> +From 940f19a51e334ac23a4bc43bbcb17dfc5cea3cf0 Mon Sep 17 00:00:00 2001
> +From: Fabrice Fontaine <fontaine.fabrice@gmail.com>
> +Date: Fri, 7 Jun 2019 23:17:13 +0200
> +Subject: [PATCH] meson.build: fix static build with gcrypt
> +
> +Use dependency instead of cc.find_library to find gcrypt dependencies
> +such as gpg-error otherwise static build will fail
> +
> +Fixes:
> + - http://autobuild.buildroot.net/results/fb698e3e903869978bd5e69d791ec362317b7981
> +
> +Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
> +[Upstream status: https://github.com/iputils/iputils/pull/185]
for reviewers: nack as this one is broken.

Kind regards,
Petr

      reply	other threads:[~2019-06-07 22:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-07 21:49 [Buildroot] [PATCH 1/1] package/iputils: fix static build with gcrypt Fabrice Fontaine
2019-06-07 22:12 ` Petr Vorel [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=20190607221224.GA4673@x230 \
    --to=petr.vorel@gmail.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.