make: failing jail cleanup is not fatal
In some cases jail cleaning up may fail. In such a case, we still want to be able to build a fresh set of binaries, which are used to run coolwsd --cleanup. Since cleaning up the jails and the systemplate are not strictly required to building, we now only emmit a warning and move on. Change-Id: I4ebf7772cf767b579810247c427d86efa5a6d3ad Signed-off-by: Ashod Nakashian <ashod.nakashian@collabora.co.uk>
This commit is contained in:
parent
f59dd62f6f
commit
9e8238310c
1 changed files with 2 additions and 2 deletions
|
@ -436,8 +436,8 @@ clean-am: cleanup clean-binPROGRAMS clean-generic clean-libtool clean-local clea
|
|||
|
||||
clean-local:
|
||||
$(CLEANUP_COMMAND)
|
||||
if test "z@JAILS_PATH@" != "z"; then rm -rf "@JAILS_PATH@"; fi
|
||||
if test "z@SYSTEMPLATE_PATH@" != "z"; then rm -rf "@SYSTEMPLATE_PATH@"; fi
|
||||
if test "z@SYSTEMPLATE_PATH@" != "z"; then rm -rf "@SYSTEMPLATE_PATH@" || echo "WARNING: failed to remove the systemplate"; fi
|
||||
if test "z@JAILS_PATH@" != "z"; then rm -rf "@JAILS_PATH@" || echo "WARNING: failed to remove all jails cleanly"; fi
|
||||
rm -rf "${top_srcdir}/loleaflet"
|
||||
rm -rf loolconfig loolconvert loolforkit loolmap loolmount # kill old binaries
|
||||
rm -rf loolwsd loolwsd_fuzzer coolwsd_fuzzer loolstress loolsocketdump
|
||||
|
|
Loading…
Reference in a new issue