All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcus Folkesson <marcus.folkesson@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] libostree: override path to gpg-error-config
Date: Thu, 26 Jul 2018 10:05:34 +0200	[thread overview]
Message-ID: <20180726080534.GA29310@gmail.com> (raw)
In-Reply-To: <6af2fcd3-69fc-a228-6bb1-d00cc9e67d1f@mind.be>

On Thu, Jul 26, 2018 at 09:56:31AM +0200, Arnout Vandecappelle wrote:
> 
> 
> On 26-07-18 09:42, Marcus Folkesson wrote:
> > libostree has begun to use `gpg-error-config` in their configuration
> > script.
> > Point out gpg-error-config in staging dir to avoid using the one
> > installed on the host system.
> > 
> > Fixes:
> >  http://autobuild.buildroot.net/results/447b96e449e881cf1bd9644cda0f386aa4c75724
> > 
> > Signed-off-by: Marcus Folkesson <marcus.folkesson@gmail.com>
> > ---
> >  package/libostree/libostree.mk | 1 +
> >  1 file changed, 1 insertion(+)
> > 
> > diff --git a/package/libostree/libostree.mk b/package/libostree/libostree.mk
> > index 24eda0d1db..4d0b38fc9e 100644
> > --- a/package/libostree/libostree.mk
> > +++ b/package/libostree/libostree.mk
> > @@ -12,6 +12,7 @@ LIBOSTREE_LICENSE = LGPL-2.0+
> >  LIBOSTREE_LICENSE_FILES = COPYING
> >  LIBOSTREE_DEPENDENCIES = e2fsprogs host-bison host-pkgconf libfuse libglib2 libgpgme xz
> >  LIBOSTREE_INSTALL_STAGING = YES
> > +LIBOSTREE_CONF_ENV = ac_cv_path_GPG_ERROR_CONFIG=$(STAGING_DIR)/usr/bin/gpg-error-config
> 
>  We would normally use GPG_ERROR_CONFIG instead of ac_cv_path_GPG_ERROR_CONFIG.
> Is there any reason why that doesn't work?

No, I just got inspiration from other packages, so really no reason.
GPG_ERROR_CONFIG seems to work as well.

I will change that, thank you.

> 
>  Regards,
>  Arnout
> 
> >  
> >  LIBOSTREE_CONF_OPTS += \
> >  	--with-gpgme-prefix=$(STAGING_DIR)/usr \
> > 
> 
> -- 
> Arnout Vandecappelle                          arnout at mind be
> Senior Embedded Software Architect            +32-16-286500
> Essensium/Mind                                http://www.mind.be
> G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
> LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
> GPG fingerprint:  7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF


Best regards
Marcus Folkesson
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20180726/546be156/attachment.asc>

      reply	other threads:[~2018-07-26  8:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-26  7:42 [Buildroot] [PATCH] libostree: override path to gpg-error-config Marcus Folkesson
2018-07-26  7:56 ` Arnout Vandecappelle
2018-07-26  8:05   ` Marcus Folkesson [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=20180726080534.GA29310@gmail.com \
    --to=marcus.folkesson@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.