From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dan.rpsys.net (5751f4a1.skybroadband.com [87.81.244.161]) by mail.openembedded.org (Postfix) with ESMTP id CAD4D6FFD8 for ; Fri, 17 Jun 2016 22:10:33 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by dan.rpsys.net (8.14.4/8.14.4/Debian-4.1ubuntu1) with ESMTP id u5HMAU6u029730; Fri, 17 Jun 2016 23:10:30 +0100 Received: from dan.rpsys.net ([127.0.0.1]) by localhost (dan.rpsys.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id woqyai-14MMR; Fri, 17 Jun 2016 23:10:30 +0100 (BST) Received: from hex ([192.168.3.34]) (authenticated bits=0) by dan.rpsys.net (8.14.4/8.14.4/Debian-4.1ubuntu1) with ESMTP id u5HMARqK029725 (version=TLSv1/SSLv3 cipher=AES128-GCM-SHA256 bits=128 verify=NOT); Fri, 17 Jun 2016 23:10:28 +0100 Message-ID: <1466201427.25557.39.camel@linuxfoundation.org> From: Richard Purdie To: Christopher Larson , "Jolley, Stephen K" Date: Fri, 17 Jun 2016 23:10:27 +0100 In-Reply-To: References: <9ADD3FDE8B189B4AA2F8A3C711F8155E5718DD13@fmsmsx111.amr.corp.intel.com> X-Mailer: Evolution 3.16.5-1ubuntu3.1 Mime-Version: 1.0 Cc: "yocto@yoctoproject.org" , "openembedded-core@lists.openembedded.org" Subject: Re: Yocto Project Status WW25 X-BeenThere: openembedded-core@lists.openembedded.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Patches and discussions about the oe-core layer List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Jun 2016 22:10:34 -0000 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8bit 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