Re: [Lldb-commits] New llvm build server account request

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 It's fixed. It was my fault as I forgot to make updateScripts.sh available via PATH. Buildslave works properly. Thank you! On 18.11.2015 03:31, Kamil Rytarowski via lldb-commits wrote: > I've noted the first set of successfully built LLDB instance

Re: [Lldb-commits] New llvm build server account request

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 I've noted the first set of successfully built LLDB instances on NetBSD! http://lab.llvm.org:8014/builders/lldb-amd64-ninja-netbsd7/builds/973 I've stopped the buildbot on the Staging server and redirected port to port 9990. There are some issues

Re: [Lldb-commits] New llvm build server account request

Done. Please let me know if it works for you. Thanks, Ying On Tue, Nov 17, 2015 at 3:34 AM, Kamil Rytarowski wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > Hello Ying, > > Regarding the NetBSD buildbot for LLDB one NetBSD we need a tweak. > > Please test for the existence (only

Re: [Lldb-commits] New llvm build server account request

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hello Ying, Regarding the NetBSD buildbot for LLDB one NetBSD we need a tweak. Please test for the existence (only on NetBSD) of a file /usr/include/panel.h. If it's missing please add '-DLLDB_DISABLE_CURSES' to CMake configure arguments. if [ ! -

Re: [Lldb-commits] New llvm build server account request

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Please update the documentation from http://lldb.llvm.org/build.html#BuildingLldbOnLinux. and add an entry for NetBSD: On NetBSD one might run: > pkgin install swig python27 Regarding the cmake issue, I suggest to add this change to cmake.sh: if [

Re: [Lldb-commits] New llvm build server account request

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 My $CC/$CXX is GCC 4.8.5. I have good reason for it - to not intermix system-wide and fetched headers for llvm. In the past this was causing problems for me during my lldb porting. Please update my builder.py for using gcc. On 21.10.2015 03:11, Yi

Re: [Lldb-commits] New llvm build server account request

Submitted the change, http://reviews.llvm.org/rL250871 The problem you mentioned has been resolved. But clang is missing from your system. You need to make sure the system is able to build and test lldb. Follow this http://lldb.llvm.org/build.html#BuildingLldbOnLinux. On Tue, Oct 20, 2015 at 5:4

Re: [Lldb-commits] New llvm build server account request

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 http://lab.llvm.org:8014/builders/lldb-amd64-ninja-netbsd7/builds/90 cmake.sh is still wrong: #!/bin/bash -e set -x host=$(uname) if [[ $host != Linux ]]; then echo "Skip cmake step for" $host else source setEnv.sh mkdir -p $buildDir cd $bu

Re: [Lldb-commits] New llvm build server account request

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 21.10.2015 02:03, Ying Chen wrote: > > > On Tue, Oct 20, 2015 at 4:46 PM, Kamil Rytarowski > wrote: > > It just appeared there. > > I took your updateScripts.sh, moved it to my $PATH. Is it > everything? > > >> Please a

Re: [Lldb-commits] New llvm build server account request

On Tue, Oct 20, 2015 at 4:46 PM, Kamil Rytarowski wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > It just appeared there. > > I took your updateScripts.sh, moved it to my $PATH. Is it everything? Please also put the test_cfg.json to this location, /home/motus/build/build/. A dumm

Re: [Lldb-commits] New llvm build server account request

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 It just appeared there. I took your updateScripts.sh, moved it to my $PATH. Is it everything? Will the rest of the scripts from https://android.googlesource.com/platform/external/lldb-utils/+/lldb-mas ter-dev/buildbotScripts/bashShell/svntotbuild/

Re: [Lldb-commits] New llvm build server account request

Please check again. Please note that this file needs to be included in your PATH. The rest of the scripts don't have to. Sample of test configuration file could be found here. https://android.googlesource.com/platform/external/lldb-utils/+/lldb-master-dev/buildbotScripts/testCfg/ On Tue, Oct 20, 2

Re: [Lldb-commits] New llvm build server account request

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Where can I find this updateScripts.sh? It's missing under your link: https://android.googlesource.com/platform/external/lldb-utils/+/lldb-mas ter-dev/buildbotScripts/bashShell/svntotbuild/ On 21.10.2015 00:29, Ying Chen wrote: > Hello Kamil, Galin

Re: [Lldb-commits] New llvm build server account request

Hello Kamil, Galina, If you would like to build LLDB with cmake and ninja, I suggest to consider the following two factory functions. Depends on what you described, I feel the first one works better for you. 1. getLLDBUbuntuCMakeBuildFactory If you only run local lldb tests, this is the factory t

Re: [Lldb-commits] New llvm build server account request

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hello Ying, I'm in trouble with my attempts to connect my NetBSD/amd64 machine to the LLDB/LLVM build zone. My host is NetBSD-7.0 (with buildslave ID: lldb-amd64-ninja-netbsd7). I use pkgsrc (2015Q3) to ship packages. I'm attaching a list of instal

Re: [Lldb-commits] New llvm build server account request

Hello Kamil, It looks like you are missing dependencies for the LLDB builder you have chosen. http://lab.llvm.org:8014/builders/lldb-amd64-ninja-netbsd7/builds/75/steps/update%20scripts/logs/stdio The getLLDBScriptCommandsFactory build factory does not document the assumed dependency, so you may