From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Julien Olivain <ju.o@free.fr>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/libgpgme: always use gpgrt-config from buildroot staging
Date: Sat, 2 Sep 2023 09:35:59 +0200 [thread overview]
Message-ID: <20230902093559.7a2dae24@windsurf> (raw)
In-Reply-To: <20230901220659.522842-1-ju.o@free.fr>
On Sat, 2 Sep 2023 00:06:58 +0200
Julien Olivain <ju.o@free.fr> wrote:
> gpgme updated its gpg-error.m4 macro files to detect gpgrt-config at
> several occasions. Those changes are included since buildroot commit
> 13f3b8e124 "package/libgpgme: bump to version 1.20.0".
>
> gpgrt-config path needs to be forced in _CONF_ENV to make sure it
> will work in all host environments. See the log entry of commit
> d7f2d8403e "package/gnupg2: fix build failure when host provides an
> old gpgrt-config" [2] for a complete explanation.
>
> [1] https://git.gnupg.org/cgi-bin/gitweb.cgi?p=gpgme.git;a=history;f=m4/gpg-error.m4;h=gpgme-1.20.0
> [2] https://git.buildroot.org/buildroot/commit/?id=d7f2d8403ec82f3b1772ec17bf1df8c42987a1f8
>
> Signed-off-by: Julien Olivain <ju.o@free.fr>
> ---
> package/libgpgme/libgpgme.mk | 4 ++++
> 1 file changed, 4 insertions(+)
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2023-09-02 7:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-01 22:06 [Buildroot] [PATCH 1/1] package/libgpgme: always use gpgrt-config from buildroot staging Julien Olivain
2023-09-02 7:35 ` Thomas Petazzoni via buildroot [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=20230902093559.7a2dae24@windsurf \
--to=buildroot@buildroot.org \
--cc=ju.o@free.fr \
--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.