Re: broken ncurses support for python

[Scott Garman <scott.a.garman@intel.com>]

On 03/06/2012 05:06 AM, Sergey Lapin wrote:
> On Tue, Mar 6, 2012 at 3:08 PM, Sergey Lapin<slapinid@gmail.com>  wrote:
>> commit dd05e06b89906002f68d616a6326c962e725bc54
>> Author: Christopher Larson<chris_larson@mentor.com>
>> Date:   Tue Jan 10 13:51:18 2012 -0600
>>
>>     ncurses-native: install to libdir, not base_libdir
>
> I was wrong with this one, actual culprit is this one:
>
> commit 796c3d038fb7892a5e5206fb10217623de18853f
> Author: Scott Garman<scott.a.garman@intel.com>
> Date:   Wed Jan 4 22:30:29 2012 -0800
>
>
>>
>> breaks python ncurses support.
>>
>> Any ideas on proper fixing? For myself I revert this locally and
>> everything works perfectly.
>> (I think .so files and .a archives should be in usr/lib while .so
>> can go to /lib which is not the case with current ncurses.)
>> so mv in do_install should be sufficient, not --libdir=${base_libdir}.

Could you be more specific about how python ncurses support is broken? I 
assume you're getting errors of unresolved symbols. If that's the case, 
you may need to rebuild the application so it links to ncurses from 
base_libdir.

Scott

-- 
Scott Garman
Embedded Linux Engineer - Yocto Project
Intel Open Source Technology Center