From owner-freebsd-testing@FreeBSD.ORG Tue Mar 10 23:49:48 2015 Return-Path: Delivered-To: freebsd-testing@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D9EEEE4D; Tue, 10 Mar 2015 23:49:48 +0000 (UTC) Received: from mail-la0-x234.google.com (mail-la0-x234.google.com [IPv6:2a00:1450:4010:c03::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 484407F7; Tue, 10 Mar 2015 23:49:48 +0000 (UTC) Received: by labgm9 with SMTP id gm9so5245024lab.11; Tue, 10 Mar 2015 16:49:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=kUAVfzmpdCsVcb8oV+k3MYV22b8DOlB/mgMSjLUwKvc=; b=ifwBDzRzziUfYdIbIfCQaYR1sorivxyZFUxkvY4hfbN/jkimaPgNH0UyYexhxHhRUF rfMcmP5cKfGlD99cIBUOtrf2PMVwPe7BdgsPVC24O4UNnMG6t75d56nf/QjykLGZF9xc U66Hd9cRoCwOJj2hxqPM88gwgmoOCuRf4+p/spPZNnuS/+Ql6uSjDS9ty2yUwwRs60BY k0CS0g1tECrx9OBt248wBine/ZaShfEFUBuwKe+YcRYPHFw6/lw1aNsYg5tekXSCxod7 Xe+oF+d3fBe6JIQP6+QqMkRu0zesN818NqAaWXTYWWN+E3I0WAvssAJrj40RYRyaQij4 Y84g== MIME-Version: 1.0 X-Received: by 10.112.26.209 with SMTP id n17mr27359675lbg.84.1426031386313; Tue, 10 Mar 2015 16:49:46 -0700 (PDT) Sender: crodr001@gmail.com Received: by 10.112.82.164 with HTTP; Tue, 10 Mar 2015 16:49:46 -0700 (PDT) In-Reply-To: References: <1857A2A3-0C19-4F52-BCAF-6C72FE7D8DF3@FreeBSD.org> Date: Tue, 10 Mar 2015 16:49:46 -0700 X-Google-Sender-Auth: rVsrEcvOk3bD3tRQrOibIMa_O5g Message-ID: Subject: Re: Failed to build with external toolchain From: Craig Rodrigues To: Dimitry Andric Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: "freebsd-testing@freebsd.org" , freebsd-toolchain@freebsd.org X-BeenThere: freebsd-testing@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Testing on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Mar 2015 23:49:49 -0000 On Sat, Mar 7, 2015 at 3:48 PM, Dimitry Andric wrote: > On 07 Mar 2015, at 21:12, Craig Rodrigues wrote: > > I ran the build again and this time I am getting errors about undefined > > symbol utimensat(): > > > > > https://jenkins.freebsd.org/job/FreeBSD_HEAD_external_toolchain_gcc/14/console > > > > Any ideas? > > It's linking against the wrong libc, the one from the FreeBSD-10 host > system, which does not have utimensat(): > > --- cp --- > /usr/local/bin/x86_64-portbld-freebsd10.0-gcc -isystem > /builds/FreeBSD_HEAD_external_toolchain_gcc/obj/builds/FreeBSD_HEAD_external_toolchain_gcc/tmp/usr/include > -L/builds/FreeBSD_HEAD_external_toolchain_gcc/obj/builds/FreeBSD_HEAD_external_toolchain_gcc/tmp/usr/lib > -O2 -pipe -DVM_AND_BUFFER_CACHE_SYNCHRONIZED -D_ACL_PRIVATE -std=gnu99 > -fstack-protector -Wsystem-headers -Wall -Wno-format-y2k -W > -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes > -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow > -Wunused-parameter -Wcast-align -Wchar-subscripts -Winline -Wnested-externs > -Wredundant-decls -Wold-style-definition -Wno-pointer-sign -o cp cp.o > utils.o > [...] > utils.o: In function `setfile': > utils.c:(.text+0x83): undefined reference to `utimensat' > utils.c:(.text+0x1ce): undefined reference to `utimensat' > utils.c:(.text+0x38c): undefined reference to `utimensat' > collect2: error: ld returned 1 exit status > > There should probably be a --sysroot flag in there, pointing to the > ${WORLDTMP} built during the earlier stages. > > For some reason, this flag is not added for gcc, in Makefile.inc1. No > idea why that was done. > Oh, OK. So if I set CROSS_TOOLCHAIN=amd64-gcc, (1) /usr/local/share/toolchains/amd64-gcc.mk is included (2) X_COMPILER_TYPE=gcc is defined in (1) (3) This code is hit in Makefile.inc1: .if defined(X_COMPILER_TYPE) && ${X_COMPILER_TYPE} == gcc XCFLAGS+= -isystem ${WORLDTMP}/usr/include -L${WORLDTMP}/usr/lib XCXXFLAGS+= -I${WORLDTMP}/usr/include/c++/v1 -std=gnu++11 -L${WORLDTMP}/../lib/libc++ DEPFLAGS+= -I${WORLDTMP}/usr/include/c++/v1 .else TARGET_ABI?= unknown TARGET_TRIPLE?= ${TARGET_ARCH:C/amd64/x86_64/}-${TARGET_ABI}-freebsd11.0 XCFLAGS+= -target ${TARGET_TRIPLE} XCFLAGS+= --sysroot=${WORLDTMP} ${BFLAGS} XCXXFLAGS+= --sysroot=${WORLDTMP} ${BFLAGS} So does this mean that --sysroot is not set? Should it be? -- Craig From owner-freebsd-testing@FreeBSD.ORG Thu Mar 12 19:53:15 2015 Return-Path: Delivered-To: freebsd-testing@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id C46CD98B for ; Thu, 12 Mar 2015 19:53:15 +0000 (UTC) Received: from mail.turbocat.net (mail.turbocat.net [IPv6:2a01:4f8:d16:4514::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 89E15A2 for ; Thu, 12 Mar 2015 19:53:15 +0000 (UTC) Received: from laptop015.home.selasky.org (cm-176.74.213.204.customer.telag.net [176.74.213.204]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id D49D11FE023 for ; Thu, 12 Mar 2015 20:53:13 +0100 (CET) Message-ID: <5501EED7.4060801@selasky.org> Date: Thu, 12 Mar 2015 20:53:59 +0100 From: Hans Petter Selasky User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: freebsd-testing@freebsd.org Subject: Phabricator and automatic build testing Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-testing@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Testing on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Mar 2015 19:53:15 -0000 Hi, Is it possible to integrate Phabricator (reviews.freebsd.org) with automatic build testing? Keep me CC'ed, hence I'm not subscribed to this list. --HPS From owner-freebsd-testing@FreeBSD.ORG Thu Mar 12 19:59:08 2015 Return-Path: Delivered-To: freebsd-testing@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D80F5C18 for ; Thu, 12 Mar 2015 19:59:08 +0000 (UTC) Received: from mail-lb0-x234.google.com (mail-lb0-x234.google.com [IPv6:2a00:1450:4010:c04::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 54C2F124 for ; Thu, 12 Mar 2015 19:59:08 +0000 (UTC) Received: by lbdu10 with SMTP id u10so18411185lbd.4 for ; Thu, 12 Mar 2015 12:59:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=CphyM+pzwnj7L8Fvxv0cVICRTgd/1QxoM1R+W7+FsTc=; b=SImVkfNp5v/lenlVcgjK1Q3d6YNj0mxIx5w3AZKG2kNyxAnSDe5jm7AL7lTpoYq4EA qB0QReIvCtJUBrOLvuoCV5b221baDfQpynIrIf0hRhvmj9g9WVs/rCuGuFq9/m8pIx3U zU+50nQQqpl3VC6xAgKlq+lWLvMlyvTXBoeAxWQNzQxgDvQOsqL0JYi+qjgF7+/DC8Po cYTjU8aMPxVWOzwTDAQwM/9TVeqBvEA7WCVnQNDDMqkoQxeuW05X8aO+/3IGEuL32Ajw 5Y3G/vvxOoV08ECKwwA5AURhUOQN4jTz+JTWafpcGY9uzmllonDj9FKBaXTxvS3FI+B2 cf9A== MIME-Version: 1.0 X-Received: by 10.112.26.209 with SMTP id n17mr35284646lbg.84.1426190346405; Thu, 12 Mar 2015 12:59:06 -0700 (PDT) Sender: crodr001@gmail.com Received: by 10.112.82.164 with HTTP; Thu, 12 Mar 2015 12:59:06 -0700 (PDT) In-Reply-To: <5501EED7.4060801@selasky.org> References: <5501EED7.4060801@selasky.org> Date: Thu, 12 Mar 2015 12:59:06 -0700 X-Google-Sender-Auth: sxZq9s71K-04v8pcQWuz-pth2P4 Message-ID: Subject: Re: Phabricator and automatic build testing From: Craig Rodrigues To: Hans Petter Selasky Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: "freebsd-testing@freebsd.org" X-BeenThere: freebsd-testing@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Testing on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Mar 2015 19:59:08 -0000 On Thu, Mar 12, 2015 at 12:53 PM, Hans Petter Selasky wrote: > Hi, > > Is it possible to integrate Phabricator (reviews.freebsd.org) with > automatic build testing? > > Keep me CC'ed, hence I'm not subscribed to this list. > Can you describe a workflow that you would like to see with reviews.freebsd.org and automatic build testing? It is quite possible to integrate phabricator with a continuous integration system like Jenkins, for example. Here is a blog post on giving one example of how it can be done: http://www.dctrwatson.com/2013/01/jenkins-and-phabricator/ If the FreeBSD project was more tightly integrated with git and github, there would be a lot of scripts that we could instantly leverage to do this kind of thing. There are many projects that I contribute to on github, where if you do a github pull request, automated scripts build and test the change in the pull request, and report the results. In FreeBSD, we are not there yet, so we need to write the scripts to integrate with the stuff that we have, i.e. bugzilla, phabricator, jenkins, etc. The other piece of the puzzle is that someone needs to step up and do the work to make this happen with phabricator and jenkins (or whatever scripts we want to use). I've done a lot with jenkins and kyua in the past year, but I could definitely use more help from people interested in working on this stuff, and taking it to the next level. -- Craig From owner-freebsd-testing@FreeBSD.ORG Thu Mar 12 20:12:09 2015 Return-Path: Delivered-To: freebsd-testing@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 49D5AEC2; Thu, 12 Mar 2015 20:12:09 +0000 (UTC) Received: from mail.turbocat.net (mail.turbocat.net [IPv6:2a01:4f8:d16:4514::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 0ADE3353; Thu, 12 Mar 2015 20:12:09 +0000 (UTC) Received: from laptop015.home.selasky.org (cm-176.74.213.204.customer.telag.net [176.74.213.204]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id 45C0C1FE023; Thu, 12 Mar 2015 21:12:07 +0100 (CET) Message-ID: <5501F344.1030105@selasky.org> Date: Thu, 12 Mar 2015 21:12:52 +0100 From: Hans Petter Selasky User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: Craig Rodrigues Subject: Re: Phabricator and automatic build testing References: <5501EED7.4060801@selasky.org> In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Cc: "freebsd-testing@freebsd.org" X-BeenThere: freebsd-testing@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Testing on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Mar 2015 20:12:09 -0000 On 03/12/15 20:59, Craig Rodrigues wrote: > On Thu, Mar 12, 2015 at 12:53 PM, Hans Petter Selasky > wrote: > >> Hi, >> >> Is it possible to integrate Phabricator (reviews.freebsd.org) with >> automatic build testing? >> >> Keep me CC'ed, hence I'm not subscribed to this list. >> > > > Can you describe a workflow that you would like to see with > reviews.freebsd.org and automatic build testing? Hi, Sometimes it would be nice if you could check a box and say: 1) Apply the patch to 8-stable or 9-stable or 10-stable or head 2) Build universe (or all kernel or all userspace programs) Sometimes doing the universe kills a lot of time, and I frequently end up simply going into the kernel modules or programs that are affected by a change and only build those to save time. Maybe phabricator could have something similar, that you can select a set of directories and subdirectories or kernel modules to build after applying a change? Maybe also with different CFLAGS, like debug/no debug. > > It is quite possible to integrate phabricator with a continuous integration > system like Jenkins, for example. > Here is a blog post on giving one example of how it can be done: > > http://www.dctrwatson.com/2013/01/jenkins-and-phabricator/ > > If the FreeBSD project was more tightly integrated with git and github, > there would be a lot > of scripts that we could instantly leverage to do this kind of thing. > There are many projects > that I contribute to on github, where if you do a github pull request, > automated scripts > build and test the change in the pull request, and report the results. FreeBSD does have a github mirror. Can't that be used with Phabricator, if some plugins require GIT? > In FreeBSD, we are not there yet, so we need to write the scripts to > integrate with the stuff > that we have, i.e. bugzilla, phabricator, jenkins, etc. > > The other piece of the puzzle is that someone needs to step up and do the > work to make > this happen with phabricator and jenkins (or whatever scripts we want to > use). > > I've done a lot with jenkins and kyua in the past year, but I could > definitely use more help > from people interested in working on this stuff, and taking it to the next > level. I appreciate your work with Jenkins. --HPS From owner-freebsd-testing@FreeBSD.ORG Thu Mar 12 22:48:06 2015 Return-Path: Delivered-To: freebsd-testing@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 5AD8620F for ; Thu, 12 Mar 2015 22:48:06 +0000 (UTC) Received: from mail-lb0-x233.google.com (mail-lb0-x233.google.com [IPv6:2a00:1450:4010:c04::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C71E17B3 for ; Thu, 12 Mar 2015 22:48:05 +0000 (UTC) Received: by lbdu14 with SMTP id u14so19308549lbd.0 for ; Thu, 12 Mar 2015 15:48:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=2PARm8Iag0zv+p/AAVS/BUEXWiu13ANSMSjnWYEYYsc=; b=MCUL33oYx2SVl8Yv/UmGx2wNxnD03fAThUgSoqkC3TQOqqrtZFWqXWZPCKDlw0ihjz 3QPBibYllRAxy22aKp0dklJarx7b6eLG8+5vXcjAn2bv3InhH/NOJBXy5rzWmjRa72L0 GyJ1j4e1LCJXkk/BGxNq65hzKDNY99P/phMagn4tqtKqVMhl1iOB1x5ZQtUaFEpz1Ohy 7ttdHTs9+OLFLDtmi8CNNhDQlvHspGjvoGIrkHI7eWySuZC6wM5Jda4khB77vW8T9zrO 59OUjCptteXiHnaFHKFaof0YUwvW2xfH26VkMB3+82kD4Q1UdLk8A9FHbW7YBnGv7jJr J5ZQ== MIME-Version: 1.0 X-Received: by 10.152.6.71 with SMTP id y7mr28815271lay.116.1426200483672; Thu, 12 Mar 2015 15:48:03 -0700 (PDT) Sender: crodr001@gmail.com Received: by 10.112.82.164 with HTTP; Thu, 12 Mar 2015 15:48:03 -0700 (PDT) In-Reply-To: <5501F344.1030105@selasky.org> References: <5501EED7.4060801@selasky.org> <5501F344.1030105@selasky.org> Date: Thu, 12 Mar 2015 15:48:03 -0700 X-Google-Sender-Auth: Mhb74DoiSY9npk_HjkbuTpDsERY Message-ID: Subject: Re: Phabricator and automatic build testing From: Craig Rodrigues To: Hans Petter Selasky Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: "freebsd-testing@freebsd.org" X-BeenThere: freebsd-testing@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Testing on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Mar 2015 22:48:06 -0000 On Thu, Mar 12, 2015 at 1:12 PM, Hans Petter Selasky wrote: > > FreeBSD does have a github mirror. Can't that be used with Phabricator, if > some plugins require GIT? > Yes, the github mirror can be used. Right now, robak@ is working on a project whereby if someone does a github pull request against http://github.com/freebsd/freebsd, it will open a bug in the FreeBSD bugzilla system. I'm waiting to see how far he gets with this, because conceivably we could extend this to do other things like integrate with Phabricator, and trigger automated builds. One disadvantage that the FreeBSD project has is that we have multiple systems: Phabricator Bugzilla Jenkins Subversion Each system on its own is quite good. However if you want to integrate the systems together to provide more advanced workflows, we have to write code to integrate these systems. The FreeBSD project doesn't have too many coders who are willing and able to do this, so things move slowly for us. Many other open source projects have basically gone to systems where everything is integrated. Github is the most popular one by far. Others like Gitlab are popular too. There are pros and cons of using an integrated system, and relying on a third party like Github. However, when you use something like Github, there are hundreds of pre-existing scripts and workflows that you can instantly take advantage of. I have seen these other projects move at lightening speed in comparison to FreeBSD, because these integrated systems are very good, and make people productive. It will take time for FreeBSD to move in this direction, because although we have a good project, we are slow moving and resistant to change in many ways. -- Craig