similar to: Strange regression on FreeBSD buildslave regarding HP-UX scripts

Please see below. I think I know what is going on (it seems to be a make/gmake incompatibility), but to fix it, I need to rewrite some of the HP-UX packaging code, and I need a HP-UX user to help test this. Otherwise, I'm going to just rip it out for now, and add it back in when someone complains. On Feb 4, 2014, at 10:17 PM, Charles Lepple wrote: > For reasons unrelated to NUT, I

On Mon, Oct 05, 2015 at 06:12:03PM +0300, Roman Kagan wrote: > On Mon, Oct 05, 2015 at 02:17:52PM +0100, Richard W.M. Jones wrote: > > On Mon, Oct 05, 2015 at 03:40:01PM +0300, Roman Kagan wrote: > > > -guestsdir="$(cd ../tests/guests && pwd)" > > > -f="$guestsdir/windows.img" > > > +abs_top_builddir="$(cd ..; pwd)" >

Hi, i got this error during build: make[2]: Entering directory `/home/panter/ovirt/node' { test ! -d "ovirt-node-1.0.3" || { find "ovirt-node-1.0.3" -type d ! -perm -200 -exec chmod u+w {} ';' && rm -fr "ovirt-node-1.0.3"; }; } test -d "ovirt-node-1.0.3" || mkdir "ovirt-node-1.0.3" (cd gptsync && make

Hi Ovirt node image build problem? Node image build my system OS Fedora core 14. I am have a question about installation process of oVirt project. Install DOC : https://fedorahosted.org/ovirt/wiki/Build But node-image build error? [root at Ovirt-T node]# make publish { test ! -d "ovirt-node-1.9.3" || { find "ovirt-node-1.9.3" -type d ! -perm -200 -exec chmod u+w

Hi Ovirt node image build problem? Node image build my system OS Fedora core 14. I am have a question about installation process of oVirt project. Install DOC : https://fedorahosted.org/ovirt/wiki/Build But node-image build error? [root at Ovirt-T node]# ./autogen.sh I am going to run ./configure with no arguments - if you wish to pass any to it, please specify them on the

On Mon, Oct 05, 2015 at 05:05:32PM +0100, Richard W.M. Jones wrote: > On Mon, Oct 05, 2015 at 06:12:03PM +0300, Roman Kagan wrote: > > On Mon, Oct 05, 2015 at 02:17:52PM +0100, Richard W.M. Jones wrote: > > > This doesn't appear in EXTRA_DIST, so it won't be copied to the tarball. > > > > Didn't know that. How is the tarball generated, so that I can test

a really good idea Charles ;-) 2007/7/11, Charles Lepple <clepple-guest at alioth.debian.org>: > Author: clepple-guest > Date: Wed Jul 11 03:20:44 2007 > New Revision: 1025 > > Log: > Added bash completion script for 'upsc'. > ... you should also consider adding a Makefile + configure test for auto installation (based upon the existence of

Hi, I was trying to create complete rpm package for my system, containing dovecot 1.2.5 intregrated with dovecot-sieve and dovecot-managesieve. Finally I succeeded and it works great, but I found something that might be treated as wrong behaviour... When you run ./configure --with-docs=no, Makefile does not build docs anymore, but... installs them anyway :) It caused some troubles because

> The Buildbot has detected a new failure of Ubuntu-maverick-x86 on > Network UPS Tools. > Full details are available at: > http://buildbot.networkupstools.org/public/nut/builders/Ubuntu-maverick-x86/builds/39 Looks like the nutscan-snmp.h file has not been checked into the branch: make[3]: Entering directory `/var/lib/buildbot/buildbot-slave-cayenne/

If configured with --without-ocaml, the build might fail because the fix added in df5bd5741b37da9cf97d7a76ac2805557aa630db was not active. According to the automake documentation, it should be enough to set BUILT_SOURCES. --- builder/Makefile.am | 10 +--------- 1 file changed, 1 insertion(+), 9 deletions(-) diff --git a/builder/Makefile.am b/builder/Makefile.am index e3d37667b..3c7113eee 100644

Otherwise, automake will fail to process vivified/code/Makefile.am --- configure.ac | 1 + 1 files changed, 1 insertions(+), 0 deletions(-) diff --git a/configure.ac b/configure.ac index a3e186b..0e28374 100644 --- a/configure.ac +++ b/configure.ac @@ -300,6 +300,7 @@ else AC_MSG_NOTICE([Vivified was not enabled.]) fi AM_CONDITIONAL(HAVE_VIVI, [test "x$HAVE_VIVI" = xyes])

modified ovirt-node-image for inclusion in Fedora Removes ovirt-node-image-pxe sub package adds get-ovirt-node-image script adds generate-ovirt-node-pxe-tree script (replaces subpackage) moved all the scripts/tools into tools subdir adds new rpm, ovirt-node-recipe includes tools, manifests, and ks file/recipe Process for building upstream ovirt node packages.... 1. Build ovir-node.rpm in koji

You don't really need to use the llvm builders infrastructure, just setup a local jenkins (or whatever) bot that triggers from the llvm svn, see http://stackoverflow.com/questions/10014252/jenkins-ci-how-to-trigger-builds-on-svn-commit 2016-05-27 22:26 GMT+03:00 Asiri Rathnayake via cfe-dev < cfe-dev at lists.llvm.org>: > Hi Galina, > > I would like to setup a silent

How do we register buildslaves with the llvm buildbot? We run buildbot internally for clang/llvm. We would like to register our buildslaves with the official llvm buildbot. reed

Hi Galina, I would like to setup a silent buildslave for some experiments. Essentially, I would like to receive build requests from the llvm master buildbot, do my local builds but not publish results on the main buildbot (or complain to users when the builds fail). Would such a setup be possible? I looked at the documentation [1] but that seems to describe a normal buildslave setup. Thanks. /

Hi Reed, > How do we register buildslaves with the llvm buildbot? you point it at lab.llvm.org port 9990 and send the buildslave name and password to Galina. Ciao, Duncan.

Reid, I think it is the first time it is run that the errors occcur !? Not sure but that would seem logical. Aaron

Hi Brian, The Atom1-buildbot buildslave has been failing for a few days but I don't think the problem lies in the LLVM/Clang source. From the logs at http://lab.llvm.org:8011/builders/clang-atom-d2700-ubuntu-rel/builds/13632 (and newer builds): ******************** TEST 'Clang :: Driver/x86_features.s' FAILED ******************** Test has no run line!

Hi, as raghesh already posted in a previous mail, we would like to add some Polly buildslaves to the buildmaster. I just finished to set up the buildslave and now need someone to add my password to the config files. As Daniel seems to be on leave, I wonder who else has access to this machine? Cheers and thanks Tobi

Hi Asiri, You can use your local master for this or use silent master. Silent buildbot is currently copy of llvm buildbot, but does not sent any notifications. The both have the same set of builders and it's easy to switch a slave between them. To add slave/builder please add your slave and builder to zorg, but point your slave to silent master: use lab.llvm.org:9994 instead of