Re: [lldb-dev] Making LLVM_DEFAULT_TARGET_TRIPLE available to lldb's cmakery

2019-10-30 Thread Jim Ingham via lldb-dev
Yeah, I take that part back. It sort of makes sense that you build the server for the architecture you are building binaries for, since the server has to run wherever the binaries run. If we were being strict about that, we'd build one server for each backend we build clang for, but we don't d

Re: [lldb-dev] Making LLVM_DEFAULT_TARGET_TRIPLE available to lldb's cmakery

2019-10-30 Thread Ted Woodward via lldb-dev
I'm not going to comment on the change (my cmake knowledge is a hair more than yours, but not enough for this), but LLVM_DEFAULT_TARGET_TRIPLE is the default backend. LLVM_HOST_TRIPLE is the triple we're running on. In your example, LLVM_DEFAULT_TARGET_TRIPLE should be something like arm-apple-d

Re: [lldb-dev] Making LLVM_DEFAULT_TARGET_TRIPLE available to lldb's cmakery

2019-10-30 Thread Davide Italiano via lldb-dev
On Wed, Oct 30, 2019 at 11:52 AM Jim Ingham via lldb-dev wrote: > > Except of course without the comment markers... > > > On Oct 30, 2019, at 11:36 AM, Jim Ingham wrote: > > > > Anyway, another way to do this would be something like: > > > > #if (${LLVM_DEFAULT_TARGET_TRIPLE}) > > string(REGEX M

Re: [lldb-dev] Making LLVM_DEFAULT_TARGET_TRIPLE available to lldb's cmakery

2019-10-30 Thread Jim Ingham via lldb-dev
Except of course without the comment markers... > On Oct 30, 2019, at 11:36 AM, Jim Ingham wrote: > > Anyway, another way to do this would be something like: > > #if (${LLVM_DEFAULT_TARGET_TRIPLE}) > string(REGEX MATCH "^[^-]*" LLDB_DEBUGSERVER_ARCH > "${LLVM_DEFAULT_TARGET_TRIPLE}") > #else(

[lldb-dev] Making LLVM_DEFAULT_TARGET_TRIPLE available to lldb's cmakery

2019-10-30 Thread Jim Ingham via lldb-dev
Hi, all... Saleem submitted a patch to work around some other changes in llvm cmakery that was making LLVM_DEFAULT_TARGET_TRIPLE undefined when lldb went to use it for the macOS debugserver build. That was: commit 55eec2ba96bd9c19ccb5d4d13cb8c88d4abcebc6 Author: Saleem Abdulrasool Date: Tue

[lldb-dev] [Bug 43852] New: FTBFS: file INSTALL cannot find "/builddir/build/BUILD/lldb-9.0.0.src/clr-build/./lib64/python3.7".

2019-10-30 Thread via lldb-dev
https://bugs.llvm.org/show_bug.cgi?id=43852 Bug ID: 43852 Summary: FTBFS: file INSTALL cannot find "/builddir/build/BUILD/lldb-9.0.0.src/clr-build/./lib6 4/python3.7". Product: lldb Version: 9.0 Hardware

[lldb-dev] RFC: DWZ = DW_TAG_imported_unit + separate DWARF common file

2019-10-30 Thread Jan Kratochvil via lldb-dev
Hi, I would like to get a design approval before I do all remaining technical cleanups of (3) below. It was discussed before at: [lldb-dev] RFC for DWZ = DW_TAG_imported_unit + DWARF-5 supplementary files https://lists.llvm.org/pipermail/lldb-dev/2017-August/012656.html M

Re: [lldb-dev] issue with lldb9 and python3.5

2019-10-30 Thread Pavel Labath via lldb-dev
On 30/10/2019 11:18, Kamil Rytarowski wrote: On 30.10.2019 11:06, Pavel Labath wrote: On 29/10/2019 21:40, Christos Zoulas wrote: On Oct 29,  6:54pm, pa...@labath.sk (Pavel Labath) wrote: -- Subject: Re: [lldb-dev] issue with lldb9 and python3.5 | On 29/10/2019 09:31, Serge Guelton via lldb-de

Re: [lldb-dev] issue with lldb9 and python3.5

2019-10-30 Thread Kamil Rytarowski via lldb-dev
On 30.10.2019 11:06, Pavel Labath wrote: > On 29/10/2019 21:40, Christos Zoulas wrote: >> On Oct 29,  6:54pm, pa...@labath.sk (Pavel Labath) wrote: >> -- Subject: Re: [lldb-dev] issue with lldb9 and python3.5 >> >> | On 29/10/2019 09:31, Serge Guelton via lldb-dev wrote: >> | > On Mon, Oct 28, 2019

Re: [lldb-dev] issue with lldb9 and python3.5

2019-10-30 Thread Pavel Labath via lldb-dev
On 29/10/2019 21:40, Christos Zoulas wrote: On Oct 29, 6:54pm, pa...@labath.sk (Pavel Labath) wrote: -- Subject: Re: [lldb-dev] issue with lldb9 and python3.5 | On 29/10/2019 09:31, Serge Guelton via lldb-dev wrote: | > On Mon, Oct 28, 2019 at 10:09:53AM -0700, Adrian McCarthy wrote: | >> +1 Ye