All of lore.kernel.org
 help / color / mirror / Atom feed
From: Leonardo Sandoval <leonardo.sandoval.gonzalez@linux.intel.com>
To: Mark Hatle <mark.hatle@windriver.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] gpgme: Fix issue building for the target
Date: Tue, 07 Mar 2017 11:00:09 -0600	[thread overview]
Message-ID: <1488906009.3261.18.camel@linux.intel.com> (raw)
In-Reply-To: <1488902424-9496-2-git-send-email-mark.hatle@windriver.com>

Mark, pachtest complained with this series. (manually copying and
pasting stuff from the latter tool, posted in patchwork)

On Tue, 2017-03-07 at 10:00 -0600, Mark Hatle wrote:
> gpgme failed when configuring since you can only configure for one python
> system at a time (via the inherits).  So we need to have a PACKAGECONFIG
> that defines which one [or neither] you want to use.
> 
> The prior pkgconfig patch introduced the usage of the variable PKG_CONFIG,
> which is not defined anywhere.  Define this.
> 
> When building the python module, we can not call gpg-error-config, so we
> need to find an alternative way of finding the information the setup.py.in
> requires.  (In this case, it's easy to just use the environment
> STAGING_INCDIR.)
> 
> Signed-off-by: Mark Hatle <mark.hatle@windriver.com>
> ---
>  .../gpgme/gpgme/python-lang-config.patch           | 50 ++++++++++++++++++++++
>  meta/recipes-support/gpgme/gpgme_1.8.0.bb          | 28 +++++++++++-
>  2 files changed, 77 insertions(+), 1 deletion(-)
>  create mode 100644 meta/recipes-support/gpgme/gpgme/python-lang-config.patch
> 
> diff --git a/meta/recipes-support/gpgme/gpgme/python-lang-config.patch b/meta/recipes-support/gpgme/gpgme/python-lang-config.patch

* Issue             Added patch file is missing Upstream-Status in the
header [test_upstream_status_presence] 
  Suggested fix    Add Upstream-Status: <status> to the header of
meta/recipes-support/gpgme/gpgme/python-lang-config.patch (possible
values: Pending, Submitted, Accepted, Backport, Denied, Inappropriate)






      parent reply	other threads:[~2017-03-07 16:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-07 16:00 [PATCH] Fix gpgme when building for the target Mark Hatle
2017-03-07 16:00 ` [PATCH] gpgme: Fix issue " Mark Hatle
2017-03-07 16:08   ` Burton, Ross
2017-03-07 16:39     ` Mark Hatle
2017-03-07 17:00   ` Leonardo Sandoval [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=1488906009.3261.18.camel@linux.intel.com \
    --to=leonardo.sandoval.gonzalez@linux.intel.com \
    --cc=mark.hatle@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    /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.