From: Scott Garman <scott.a.garman@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: broken ncurses support for python
Date: Sat, 10 Mar 2012 14:31:18 -0800 [thread overview]
Message-ID: <4F5BD636.2050609@intel.com> (raw)
In-Reply-To: <4F5B35CF.4090001@opendreambox.org>
On 03/10/2012 03:06 AM, Andreas Oberritter wrote:
> Hello Scott,
>
> On 10.03.2012 05:57, Scott Garman wrote:
>> I filed bug #2070 to track this and have created the following fix for it:
>>
>> http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/commit/?h=sgarman/python-ncurses-fix&id=23c73da5f13b6c586353edb8143fa21058bf3a55
>
> this will break if libdir equals base_libdir. A conditional is required
> around mkdir and mv.
Hi Andreas,
Good catch - my build testing uncovered this and I've made that and some
other changes as well.
Thanks,
Scott
--
Scott Garman
Embedded Linux Engineer - Yocto Project
Intel Open Source Technology Center
prev parent reply other threads:[~2012-03-10 22:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-06 11:08 broken ncurses support for python Sergey Lapin
2012-03-06 13:06 ` Sergey Lapin
2012-03-06 19:20 ` Scott Garman
2012-03-06 22:33 ` Sergey Lapin
2012-03-08 18:48 ` Scott Garman
2012-03-10 4:57 ` Scott Garman
2012-03-10 11:06 ` Andreas Oberritter
2012-03-10 22:31 ` Scott Garman [this message]
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=4F5BD636.2050609@intel.com \
--to=scott.a.garman@intel.com \
--cc=openembedded-core@lists.openembedded.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