90-build-vm.mk: better error reference

In this case it's rather worth it to examine build.log than read documentation again (as vm.txt should have been read or at least skimmed through to get sudo setup ready, and the problem might be either an environment one or a bug).

90-build-vm.mk: better error reference
d28950ca · Michael Shigorin · 04a5f363 · d28950ca
Commit d28950ca authored Jan 14, 2017 by Michael Shigorin
Hide whitespace changes
Inline Side-by-side

Showing with 1 addition and 1 deletion

90-build-vm.mk features.in/build-vm/lib/90-build-vm.mk +1 -1

No files found.
--- a/features.in/build-vm/lib/90-build-vm.mk
+++ b/features.in/build-vm/lib/90-build-vm.mk
@@ -25,7 +25,7 @@ prepare-image: check-sudo
 	fi; \
 	if ! sudo $(TOPDIR)/bin/tar2fs \
 		"$(VM_TARBALL)" "$(VM_RAWDISK)"  $(VM_SIZE) $(VM_FSTYPE); then \
-		echo "** error: sudo tar2fs failed, see also doc/vm.txt" >&2; \
+		echo "** error: sudo tar2fs failed, see build log" >&2; \
 		exit 1; \
 	fi