From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Christopher Larson <clarson@kergoth.com>,
"Jolley, Stephen K" <stephen.k.jolley@intel.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>,
"openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: Yocto Project Status WW25
Date: Fri, 17 Jun 2016 23:10:27 +0100 [thread overview]
Message-ID: <1466201427.25557.39.camel@linuxfoundation.org> (raw)
In-Reply-To: <CABcZANkPQBWukZTtzz69JQZHOFRpnXyPV1BvP8Bv-CZqqRtSkA@mail.gmail.com>
On Fri, 2016-06-17 at 14:42 -0700, Christopher Larson wrote:
> On Fri, Jun 17, 2016 at 8:31 AM, Jolley, Stephen K <
> stephen.k.jolley@intel.com> wrote:
> > · There is a multilib issue related to the layout of the
> > host libraries leaking into python’s build process which we’re
> > struggling to debug
> Could I get some details on this? I've seen something like this where
> cmake and automake are relying on sys.lib from python3-native/python
> -native to determine the sitepackages directory, is that the behavior
> others are hitting? So python modules end up in /usr/lib/ rather than
> /usr/lib64/, for example?
>
> If that's the issue in question, the issue is the mismatch between
> the native sys.lib and target. We already patch automake to fall back
> to using our libdir + python version to determine the path, but only
> if it wasn't able to use sys.lib to do so. If we change that to
> always use libdir+python version, it should fix the automake
> packages. Then we might need to patch FindPythonLibs in cmake to do
> the same. I'm testing the automake change locally now.
https://bugzilla.yoctoproject.org/show_bug.cgi?id=9717 is the bug
Cheers,
Richard
next prev parent reply other threads:[~2016-06-17 22:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-17 15:31 Yocto Project Status WW25 Jolley, Stephen K
2016-06-17 21:42 ` Christopher Larson
2016-06-17 22:10 ` Christopher Larson
2016-06-17 22:10 ` Richard Purdie [this message]
2016-06-21 14:59 ` [yocto] " Leonardo Sandoval
-- strict thread matches above, loose matches on Subject: below --
2015-06-19 14:43 Jolley, Stephen K
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=1466201427.25557.39.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=clarson@kergoth.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=stephen.k.jolley@intel.com \
--cc=yocto@yoctoproject.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox