From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/libp11: fix enginesdir
Date: Thu, 9 May 2024 23:10:50 +0200 [thread overview]
Message-ID: <20240509231050.5365ecf0@windsurf> (raw)
In-Reply-To: <20240509204218.77779-1-fontaine.fabrice@gmail.com>
On Thu, 9 May 2024 22:42:18 +0200
Fabrice Fontaine <fontaine.fabrice@gmail.com> wrote:
> pkg-config doesn't return a libcrypto enginesdir prefixed with the
> sysroot so drop unneeded call to xargs, readlink and sed
>
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
> ---
> package/libp11/libp11.mk | 4 +---
> 1 file changed, 1 insertion(+), 3 deletions(-)
>
> diff --git a/package/libp11/libp11.mk b/package/libp11/libp11.mk
> index cd4ed34297..dc489758aa 100644
> --- a/package/libp11/libp11.mk
> +++ b/package/libp11/libp11.mk
> @@ -11,10 +11,8 @@ LIBP11_INSTALL_STAGING = YES
> LIBP11_LICENSE = LGPL-2.1+
> LIBP11_LICENSE_FILES = COPYING
>
> -# pkg-config returns a libcrypto enginesdir prefixed with the sysroot,
> -# so let's rip it out.
Well, this workaround was here for a reason. Since when it is no longer
needed?
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2024-05-09 21:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-09 20:42 [Buildroot] [PATCH 1/1] package/libp11: fix enginesdir Fabrice Fontaine
2024-05-09 21:10 ` Thomas Petazzoni via buildroot [this message]
2024-07-22 20:21 ` Thomas Petazzoni via buildroot
2024-07-22 20:47 ` Fabrice Fontaine
2024-08-07 9:00 ` Thomas Petazzoni via buildroot
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=20240509231050.5365ecf0@windsurf \
--to=buildroot@buildroot.org \
--cc=fontaine.fabrice@gmail.com \
--cc=thomas.petazzoni@bootlin.com \
/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.