In the majority of cases, developers debugging their code using vagrant will be more interested in compiler errors/warnings than the exact invocation of the compiler. By enabling silent-rules, the verbosity of compilation is lowered and it is easier to identify these pieces of information.
Signed-off-by: Joe Stringer <j...@ovn.org> --- Vagrantfile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Vagrantfile b/Vagrantfile index a3d444d366ba..d7cf73738e75 100644 --- a/Vagrantfile +++ b/Vagrantfile @@ -20,7 +20,7 @@ SCRIPT $configure_ovs = <<SCRIPT mkdir -p ~/build cd ~/build -/vagrant/configure --with-linux=/lib/modules/`uname -r`/build +/vagrant/configure --with-linux=/lib/modules/`uname -r`/build --enable-silent-rules SCRIPT $build_ovs = <<SCRIPT -- 2.8.2 _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
