[lldb-dev] Losing prompt when running any python commands

Matthew Sorrels sorrels.m at gmail.com
Fri Jul 5 09:13:36 PDT 2013

I think the license should be fine, but I'm not a lawyer.  The real
question is how would you like it integrated in?  I'll take a look at
pexpect and see how it was merged in.  At the very least I assume you'll
want some way to allow the build system to use the system version instead.
Is there anything else that it needs to do?

On Thu, Jul 4, 2013 at 11:13 AM, Malea, Daniel <daniel.malea at intel.com>wrote:

>  What are your concerns with checking in an updated libedit (or another
> similar library like the zsh that Greg mentioned)? As far as I understand,
> the BSD licensing is permissive enough to do that, and there's other
> (albeit less critical) libraries checked into the LLDB source tree, such as
> pexpect.
>  Dan
>   From: Matthew Sorrels <sorrels.m at gmail.com>
> Date: Wednesday, 3 July, 2013 8:21 PM
> To: Greg Clayton <gclayton at apple.com>
> Cc: "lldb-dev at cs.uiuc.edu" <lldb-dev at cs.uiuc.edu>
> Subject: Re: [lldb-dev] Losing prompt when running any python commands
>  I'm not sure we really want to move it into lldb though, but I'd say
> it's definitely a requirement if you want to use lldb on Linux.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/lldb-dev/attachments/20130705/a421c1ef/attachment.html>

More information about the lldb-dev mailing list