<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On 7 March 2017 at 16:00, Mark Hatle <span dir="ltr"><<a href="mailto:mark.hatle@windriver.com" target="_blank">mark.hatle@windriver.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><span class="gmail-il">gpgme</span> failed when configuring since you can only configure for one python<br>
system at a time (via the inherits). So we need to have a PACKAGECONFIG<br>
that defines which one [or neither] you want to use.<br>
<br>
The prior pkgconfig patch introduced the usage of the variable PKG_CONFIG,<br>
which is not defined anywhere. Define this.<br>
<br>
When building the python module, we can not call gpg-error-config, so we<br>
need to find an alternative way of finding the information the <a href="http://setup.py.in" rel="noreferrer" target="_blank">setup.py.in</a><br>
requires. (In this case, it's easy to just use the environment<br>
STAGING_INCDIR.)</blockquote></div><br><div class="gmail_extra">| checking for swig... no</div><div class="gmail_extra">| checking for swig2.0... no</div><div class="gmail_extra">| configure: error:</div><div class="gmail_extra">| ***</div><div class="gmail_extra">| *** You need SWIG to build the Python bindings.</div><div class="gmail_extra"><br></div><div class="gmail_extra">It must be finding a swig binary on your host.</div><div class="gmail_extra"><br></div><div class="gmail_extra">Ross</div></div></div>