Date: Wed, 11 Feb 2015 07:48:19 -0800 From: Craig Rodrigues <rodrigc@FreeBSD.org> To: Li-Wen Hsu <lwhsu@freebsd.org> Cc: "freebsd-testing@freebsd.org" <freebsd-testing@freebsd.org> Subject: Re: scan-build and Jenkins Message-ID: <CAG=rPVeHYn7esVq3KFHoQ_gt5p%2BE1wLT47CvKZCcePFhPr3MRw@mail.gmail.com> In-Reply-To: <20150211150515.GA22751@FreeBSD.cs.nctu.edu.tw> References: <CAG=rPVe4O_sk7LDas5MoqgafOLVPj-UPAkgYATSGPuh13Jec5A@mail.gmail.com> <20150211150515.GA22751@FreeBSD.cs.nctu.edu.tw>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Feb 11, 2015 at 7:05 AM, Li-Wen Hsu <lwhsu@freebsd.org> wrote: > Hi, > > - "Multiple SCMs" plugin is used, for check out both scan-build scripts > and source being checked > - scan-build is build from LLVM & Clang trunk, which are also checked out > by > multiple SCMs plugin and built when job triggered. This is designed > by uqs@ at the beginning because we want to use the latest tool to > eliminate false results. > Thanks, this was the part I was not sure about. I will look at the Jenkins job to see how to build scan-build. Where did you find out the steps to build scan-build? Since you are building LLVM & Clang from trunk, does that mean you are using the trunk version of Clang to build FreeBSD as well, or do you just run scan-build to run the static analysis without building the FreeBSD source tree? -- Craig
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAG=rPVeHYn7esVq3KFHoQ_gt5p%2BE1wLT47CvKZCcePFhPr3MRw>