See <https://builds.apache.org/job/Mesos-Trunk-Ubuntu-Build-In-Src/18/changes>

Changes:

[benh] Replaced all shell 'source' commands with '.' (fixes MESOS-132).

[benh] Removed "silent rules" so older (and newer apparently) build 
environments work without problems. This issue was first mentioned by John 
Sirois on Mac OS X 10.7 and documented in MESOS-126.

------------------------------------------
Started by an SCM change
Started by an SCM change
Building remotely on ubuntu4
Updating https://svn.apache.org/repos/asf/incubator/mesos/trunk
D         src/tests/jvm.hpp
D         src/tests/jvm.cpp
U         src/Makefile.am
U         src/examples/java/test-framework.in
U         src/examples/java/test-executor.in
U         src/examples/java/test-multiple-executors-framework.in
U         src/examples/java/test-exception-framework.in
U         src/examples/python/test-framework.in
U         src/examples/python/test-executor.in
U         configure.ac
U         bin/gdb-mesos-local.sh.in
U         bin/gdb-mesos-slave.sh.in
U         bin/gdb-mesos-master.sh.in
U         bin/mesos-local.sh.in
U         bin/mesos-slave.sh.in
U         bin/mesos-master.sh.in
U         Makefile.am
At revision 1235534
[Mesos-Trunk-Ubuntu-Build-In-Src] $ /bin/bash -xe 
/tmp/hudson3829089240309255241.sh
+ export JAVA_HOME=/home/jenkins/tools/java/jdk1.6.0_20-64
+ JAVA_HOME=/home/jenkins/tools/java/jdk1.6.0_20-64
+ export 
PATH=/home/jenkins/tools/java/jdk1.6.0_20-64/bin:/home/hudson/tools/java/latest1.6/bin:/usr/local/bin:/usr/bin:/bin:/usr/bin/X11:/usr/games
+ 
PATH=/home/jenkins/tools/java/jdk1.6.0_20-64/bin:/home/hudson/tools/java/latest1.6/bin:/usr/local/bin:/usr/bin:/bin:/usr/bin/X11:/usr/games
+ ./configure --with-python-headers=/usr/include/python2.6 --with-webui 
--with-java-home=/home/jenkins/tools/java/jdk1.6.0_20-64 
--with-java-headers=/home/jenkins/tools/java/jdk1.6.0_20-64/include 
--with-included-zookeeper
/tmp/hudson3829089240309255241.sh: line 8: ./configure: No such file or 
directory
Build step 'Execute shell' marked build as failure

Reply via email to