Re: [lldb-dev] [Release-testers] [6.0.0 Release] The final tag is in

2018-03-07 Thread Sylvestre Ledru via lldb-dev
Hello,

On 02/03/2018 13:17, Hans Wennborg via Release-testers wrote:
> Dear testers,
> 
> The final version of 6.0.0 has just been tagged from the branch after
> r326550. It has the same contents as -rc3 modulo release notes and one
> small x86 fix (r326393).
> 
> Please build the final binaries and upload to the sftp.
> 
> For those following along: this means llvm-6.0.0 is complete, but it
> will take a few days to get all the tarballs ready and published on
> the web page. I will send the announcement once everything is ready.
> 
> Many thanks to everyone for your hard work!
> 

Full green on Debian:
https://buildd.debian.org/status/package.php?p=llvm-toolchain-6.0

I will have a look at rebuilding the Debian archive with this version (we did 
with rc1)
over the next month.

Cheers,
Sylvestre

___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev


Re: [lldb-dev] Command history line editing

2018-03-07 Thread Jan Kratochvil via lldb-dev
On Sun, 04 Mar 2018 21:03:26 +0100, William Schmidt via lldb-dev wrote:
> lldb deserves an editing mode functionally equivalent to what bash offers.
> And since bash is open-source, it should just be a matter of grabbing the
> bash source that implements command line editing and going from there.

It is because lldb uses libedit while bash (and gdb) use readline.

I guess it has licensing reasons as readline is GPL (not LGPL) and Apple seems
to avoid GPL the family of licenses.  IANAL but I think an alternative linking
with readline while keeping the libedit compatibility still in place would not
taint LLDB by the GPL license.  And then OSes (such as Linux or for OSX is it
Homebrew?) already using GPL software could link LLDB with readline.


Jan
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev


[lldb-dev] [Bug 36630] New: LLDB SB API headers not installed anymore since r309021

2018-03-07 Thread via lldb-dev
https://bugs.llvm.org/show_bug.cgi?id=36630

Bug ID: 36630
   Summary: LLDB SB API headers not installed anymore since
r309021
   Product: lldb
   Version: unspecified
  Hardware: PC
OS: Linux
Status: NEW
  Severity: normal
  Priority: P
 Component: All Bugs
  Assignee: lldb-dev@lists.llvm.org
  Reporter: tsche...@redhat.com
CC: llvm-b...@lists.llvm.org

Since r309021 the LLDB SB API headers (e.g /usr/include/lldb/API/LLDB.h) are
not installed anymore. Previously they were installed by default.

Looking at the commit that introduced the regression it seems this is coming
from some accidentally committed changes (at least the commit message doesn't
mention anything about the excludes).

The change landed a couple of days after 5.0 was branched so this affects the
6.0 release.

commit 10e79c4459e0a6002edf2fea14432c293c5d509f
Author: Chris Bieneman 
Date:   Tue Jul 25 20:29:45 2017 +

[CMake] Cleanup unnecessary definition

This is only used in one file, and we already set it correctly on that
file, so we don't need to set this everywhere.   

git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@309021
91177308-0d34-0410-b5e6-96231b3b80d8

diff --git a/cmake/modules/LLDBConfig.cmake b/cmake/modules/LLDBConfig.cmake
index 726552675..71820c965 100644
--- a/cmake/modules/LLDBConfig.cmake
+++ b/cmake/modules/LLDBConfig.cmake
@@ -22,10 +22,6 @@ elseif(IOS)
   set(LLDB_DEFAULT_DISABLE_PYTHON 1)
 endif()

-if(IOS)
-  add_definitions(-DNO_XPC_SERVICES)
-endif()
-
 set(LLDB_DISABLE_PYTHON ${LLDB_DEFAULT_DISABLE_PYTHON} CACHE BOOL
   "Disables the Python scripting integration.")
 set(LLDB_DISABLE_CURSES ${LLDB_DEFAULT_DISABLE_CURSES} CACHE BOOL
@@ -282,6 +278,8 @@ if (NOT LLVM_INSTALL_TOOLCHAIN_ONLY)
 PATTERN ".svn" EXCLUDE
 PATTERN ".cmake" EXCLUDE
 PATTERN "Config.h" EXCLUDE
+PATTERN "lldb-*.h" EXCLUDE
+PATTERN "API/*.h" EXCLUDE
 )

   install(DIRECTORY ${CMAKE_CURRENT_BINARY_DIR}/include/
@@ -291,6 +289,8 @@ if (NOT LLVM_INSTALL_TOOLCHAIN_ONLY)
 PATTERN "*.h"
 PATTERN ".svn" EXCLUDE
 PATTERN ".cmake" EXCLUDE
+PATTERN "lldb-*.h" EXCLUDE
+PATTERN "API/*.h" EXCLUDE
 )
 endif()

-- 
You are receiving this mail because:
You are the assignee for the bug.___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev


Re: [lldb-dev] Command history line editing

2018-03-07 Thread Ted Woodward via lldb-dev
It's not just Apple that avoids GPL. Many LLVM users cannot use GPL. Adding GPL 
code to LLDB is a non-starter.

--
Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux 
Foundation Collaborative Project

> -Original Message-
> From: lldb-dev [mailto:lldb-dev-boun...@lists.llvm.org] On Behalf Of Jan
> Kratochvil via lldb-dev
> Sent: Wednesday, March 07, 2018 3:20 AM
> To: William Schmidt 
> Cc: lldb-dev@lists.llvm.org
> Subject: Re: [lldb-dev] Command history line editing
> 
> On Sun, 04 Mar 2018 21:03:26 +0100, William Schmidt via lldb-dev wrote:
> > lldb deserves an editing mode functionally equivalent to what bash offers.
> > And since bash is open-source, it should just be a matter of grabbing
> > the bash source that implements command line editing and going from there.
> 
> It is because lldb uses libedit while bash (and gdb) use readline.
> 
> I guess it has licensing reasons as readline is GPL (not LGPL) and Apple 
> seems to
> avoid GPL the family of licenses.  IANAL but I think an alternative linking 
> with
> readline while keeping the libedit compatibility still in place would not 
> taint
> LLDB by the GPL license.  And then OSes (such as Linux or for OSX is it
> Homebrew?) already using GPL software could link LLDB with readline.
> 
> 
> Jan
> ___
> lldb-dev mailing list
> lldb-dev@lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev


Re: [lldb-dev] Command history line editing

2018-03-07 Thread via lldb-dev
> -Original Message-
> From: lldb-dev [mailto:lldb-dev-boun...@lists.llvm.org] On Behalf Of Ted
> Woodward via lldb-dev
> Sent: Wednesday, March 07, 2018 9:40 AM
> To: 'Jan Kratochvil'; 'William Schmidt'; lldb-dev@lists.llvm.org
> Subject: Re: [lldb-dev] Command history line editing
> 
> It's not just Apple that avoids GPL. Many LLVM users cannot use GPL.
> Adding GPL code to LLDB is a non-starter.

License questions need to be cleared with the LLVM Foundation.
But my non-lawyer understanding is no GPL.
--paulr

___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev


Re: [lldb-dev] [Openmp-dev] [6.0.0 Release] The final tag is in

2018-03-07 Thread Simon Dardis via lldb-dev
Hi Hans,

Looks ok here. I've uploaded the binaries.

SHA256(clang+llvm-6.0.0-mipsel-linux-gnu.tar.xz)= 
5ff062f4838ac51a3500383faeb0731440f1c4473bf892258314a49cbaa66e61
SHA256(clang+llvm-6.0.0-mips-linux-gnu.tar.xz)= 
39820007ef6b2e3a4d05ec15feb477ce6e4e6e90180d00326e6ab9982ed8fe82
SHA256(clang+llvm-6.0.0-x86_64-linux-gnu-debian8.tar.xz)= 
ff55cd0bdd0b67e22d1feee2e4c84dedc3bb053401330b64c7f6ac18e88a71f1


Thanks,
Simon

From: Openmp-dev [openmp-dev-boun...@lists.llvm.org] on behalf of Hans Wennborg 
via Openmp-dev [openmp-...@lists.llvm.org]
Sent: Friday, March 2, 2018 12:17 PM
To: Release-testers
Cc: llvm-dev; cfe-dev; openmp-dev (openmp-...@lists.llvm.org); LLDB Dev
Subject: [Openmp-dev] [6.0.0 Release] The final tag is in

Dear testers,

The final version of 6.0.0 has just been tagged from the branch after
r326550. It has the same contents as -rc3 modulo release notes and one
small x86 fix (r326393).

Please build the final binaries and upload to the sftp.

For those following along: this means llvm-6.0.0 is complete, but it
will take a few days to get all the tarballs ready and published on
the web page. I will send the announcement once everything is ready.

Many thanks to everyone for your hard work!

Hans
___
Openmp-dev mailing list
openmp-...@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/openmp-dev
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev


Re: [lldb-dev] Command history line editing

2018-03-07 Thread William Schmidt via lldb-dev
readline has been around for donkeys' years. I was hacking it in MKSToolkit
back in the nineties. That implementation had a bug that hosed the
debugger's command line and a shell work-around to resolve it. Presumably,
there must be a clean-room version of readline somewhere that does not use
GPL? bash owns the command line so applications should mimic its behavior,
or at least offer a user-selectable option. Say, either emacs or vi editing
modes, as bash itself does.

Will






On Wed, Mar 7, 2018 at 11:53 AM,  wrote:

> > -Original Message-
> > From: lldb-dev [mailto:lldb-dev-boun...@lists.llvm.org] On Behalf Of Ted
> > Woodward via lldb-dev
> > Sent: Wednesday, March 07, 2018 9:40 AM
> > To: 'Jan Kratochvil'; 'William Schmidt'; lldb-dev@lists.llvm.org
> > Subject: Re: [lldb-dev] Command history line editing
> >
> > It's not just Apple that avoids GPL. Many LLVM users cannot use GPL.
> > Adding GPL code to LLDB is a non-starter.
>
> License questions need to be cleared with the LLVM Foundation.
> But my non-lawyer understanding is no GPL.
> --paulr
>
>
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev


Re: [lldb-dev] Command history line editing

2018-03-07 Thread Ted Woodward via lldb-dev
There is - editline.

 

http://thrysoee.dk/editline/

 

 

--

Qualcomm Innovation Center, Inc.

The Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux 
Foundation Collaborative Project

 

From: William Schmidt [mailto:t.william.schm...@gmail.com] 
Sent: Wednesday, March 07, 2018 1:34 PM
To: paul.robin...@sony.com
Cc: ted.woodw...@codeaurora.org; jan.kratoch...@redhat.com; 
lldb-dev@lists.llvm.org
Subject: Re: [lldb-dev] Command history line editing

 

readline has been around for donkeys' years. I was hacking it in MKSToolkit 
back in the nineties. That implementation had a bug that hosed the debugger's 
command line and a shell work-around to resolve it. Presumably, there must be a 
clean-room version of readline somewhere that does not use GPL? bash owns the 
command line so applications should mimic its behavior, or at least offer a 
user-selectable option. Say, either emacs or vi editing modes, as bash itself 
does.

 

Will








 

On Wed, Mar 7, 2018 at 11:53 AM, mailto:paul.robin...@sony.com> > wrote:

> -Original Message-
> From: lldb-dev [mailto:lldb-dev-boun...@lists.llvm.org 
>  ] On Behalf Of Ted
> Woodward via lldb-dev
> Sent: Wednesday, March 07, 2018 9:40 AM
> To: 'Jan Kratochvil'; 'William Schmidt'; lldb-dev@lists.llvm.org 
>  
> Subject: Re: [lldb-dev] Command history line editing
>
> It's not just Apple that avoids GPL. Many LLVM users cannot use GPL.
> Adding GPL code to LLDB is a non-starter.

License questions need to be cleared with the LLVM Foundation.
But my non-lawyer understanding is no GPL.
--paulr

 

___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev


Re: [lldb-dev] [cfe-dev] [Openmp-dev] [6.0.0 Release] The final tag is in

2018-03-07 Thread Diana Picus via lldb-dev
Hi,

ARM & AArch64 also up and ready:
fb00698f38ade92d11d1aa297daf4c6ea657560a
clang+llvm-6.0.0-aarch64-linux-gnu.tar.xz
c4fd61dd28a90b754d0d39f3f1f2bffcd5b38e46
clang+llvm-6.0.0-armv7a-linux-gnueabihf.tar.xz

Cheers,
Diana

On 7 March 2018 at 19:15, Simon Dardis via cfe-dev
 wrote:
> Hi Hans,
>
> Looks ok here. I've uploaded the binaries.
>
> SHA256(clang+llvm-6.0.0-mipsel-linux-gnu.tar.xz)= 
> 5ff062f4838ac51a3500383faeb0731440f1c4473bf892258314a49cbaa66e61
> SHA256(clang+llvm-6.0.0-mips-linux-gnu.tar.xz)= 
> 39820007ef6b2e3a4d05ec15feb477ce6e4e6e90180d00326e6ab9982ed8fe82
> SHA256(clang+llvm-6.0.0-x86_64-linux-gnu-debian8.tar.xz)= 
> ff55cd0bdd0b67e22d1feee2e4c84dedc3bb053401330b64c7f6ac18e88a71f1
>
>
> Thanks,
> Simon
> 
> From: Openmp-dev [openmp-dev-boun...@lists.llvm.org] on behalf of Hans 
> Wennborg via Openmp-dev [openmp-...@lists.llvm.org]
> Sent: Friday, March 2, 2018 12:17 PM
> To: Release-testers
> Cc: llvm-dev; cfe-dev; openmp-dev (openmp-...@lists.llvm.org); LLDB Dev
> Subject: [Openmp-dev] [6.0.0 Release] The final tag is in
>
> Dear testers,
>
> The final version of 6.0.0 has just been tagged from the branch after
> r326550. It has the same contents as -rc3 modulo release notes and one
> small x86 fix (r326393).
>
> Please build the final binaries and upload to the sftp.
>
> For those following along: this means llvm-6.0.0 is complete, but it
> will take a few days to get all the tarballs ready and published on
> the web page. I will send the announcement once everything is ready.
>
> Many thanks to everyone for your hard work!
>
> Hans
> ___
> Openmp-dev mailing list
> openmp-...@lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/openmp-dev
> ___
> cfe-dev mailing list
> cfe-...@lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev