From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by yocto-www.yoctoproject.org (Postfix, from userid 118) id 3D18CE009EC; Tue, 2 Jun 2015 18:36:52 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on yocto-www.yoctoproject.org X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham version=3.3.1 X-Spam-HAM-Report: * -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] Received: from smtp.webfaction.com (mail6.webfaction.com [74.55.86.74]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id AC2D1E009CC for ; Tue, 2 Jun 2015 18:36:48 -0700 (PDT) Received: from [192.168.1.10] (c-73-194-208-34.hsd1.nj.comcast.net [73.194.208.34]) by smtp.webfaction.com (Postfix) with ESMTP id CA71A211F3E5 for ; Wed, 3 Jun 2015 01:35:53 +0000 (UTC) Message-ID: <556E59F6.7060806@mindchasers.com> Date: Tue, 02 Jun 2015 21:35:50 -0400 From: Bob Cochran User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: yocto@yoctoproject.org References: <556D1937.9090602@mindchasers.com> In-Reply-To: <556D1937.9090602@mindchasers.com> Subject: Re: Question regarding python, _sysconfigdata.py, and building C extension modules on the target... X-BeenThere: yocto@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of all things Yocto Project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Jun 2015 01:36:52 -0000 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit On 06/01/2015 10:47 PM, Bob Cochran wrote: > Hi, > > While building a python 2.7 C extension module on the target (e.g., > python setup.py build) I found that I needed to modify > /usr/lib64/python2.7/_sysconfigdata.py to successfully build the module. > > I modified both CC and LDSHARE. For both, I removed > --sysroot=/build/yocto//tmp/sysroots/'. And for > LDSHARE, I added -L/lib64, so gcc_s could be found. > > I'm wondering whether this is expected behavior or perhaps a bug. > Perhaps I should have setup my environment differently for building a C > extension module on the target? > > I would appreciate any advice on the best way to rectify this so I can > use a non-modified, generated rootfs to build C extension modules on my > target. For now, I modified my setup.py to include the following in my call to Extension(): include_dirs=['/usr/include'], library_dirs=['/lib64']) However, I don't think I should need to do this, and I didn't have to do this on targets (rootfs) generated by earlier poky releases. I'll keep digging... > > I'm using poky fido (508c4cac320d) and building with a Freescale t1040 > 64bit (meta-fsl-ppc). > > Thanks > > Bob