Re: broken ncurses support for python

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

On 03/06/2012 02:33 PM, Sergey Lapin wrote:
>>>> 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.
> No, python fails to find the library.
> And it is bad practice to put develeopment files in /lib anyway.
> I think, putting .so.x.x intu lib was sufficient instead of setting
> whole libdir to /lib.
> Or development files might be moved to /usr/lib back (and .so symlink re-created
> to address this).

Thanks, I understand what you're saying now. I hope to look into this 
tomorrow and develop a fix; I've been away at a conference all week so far.

Scott

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