summaryrefslogtreecommitdiff
path: root/autogen.sh
diff options
context:
space:
mode:
authorChengwei Yang <chengwei.yang@intel.com>2013-09-24 21:25:01 +0800
committerSimon McVittie <simon.mcvittie@collabora.co.uk>2013-10-08 11:06:19 +0100
commit0d15a9035a0be37ddd8c0bda3d3a613eb87c0b62 (patch)
treee758037012291c6f8e599e089ac814e028a4b636 /autogen.sh
parent57dc720b9f25dec999fcc53da982114098cefae9 (diff)
downloaddbus-0d15a9035a0be37ddd8c0bda3d3a613eb87c0b62.tar.gz
Do not suggest user the next step after executed autogen.sh
We assume that user/developer who building dbus from source code are familiar with the standard 'autogen.sh, configure, make, make install' build process, so print such a notice doesn't make a lot of sense. In addition, on *BSD platform, the pre-installed 'make' doesn't work at all since gnu make is required. However, it named to 'gmake' on *BSD platform. So the notice will makes new comer confused. Bug: https://bugs.freedesktop.org/show_bug.cgi?id=65415 Reviewed-by: Simon McVittie <simon.mcvittie@collabora.co.uk>
Diffstat (limited to 'autogen.sh')
-rwxr-xr-xautogen.sh8
1 files changed, 1 insertions, 7 deletions
diff --git a/autogen.sh b/autogen.sh
index b9046879..bff8257b 100755
--- a/autogen.sh
+++ b/autogen.sh
@@ -101,11 +101,5 @@ else
fi
if $run_configure; then
- $srcdir/configure --enable-developer --config-cache "$@" || exit $?
- echo
- echo "Now type 'make' to compile $PROJECT."
-else
- echo
- echo "Now run 'configure' and 'make' to compile $PROJECT."
+ $srcdir/configure --enable-developer --config-cache "$@"
fi
-