libunwind is trying to build its documentation. Unless we need this documentation, we should disable building the documentation because building it wastes time and introduces new build time dependencies that aren't otherwise useful or desirable. This means that our B2G builds that are about to go live in production aren't building anymore. make: Leaving directory `/builds/slave/m-cen-b2g/build/obj-b2g/tools/profiler/libunwind/src/tests' Making all in doc make: Entering directory `/builds/slave/m-cen-b2g/build/obj-b2g/tools/profiler/libunwind/src/doc' latex2man -t /builds/slave/m-cen-b2g/build/tools/profiler/libunwind/src/doc/libunwind.trans /builds/slave/m-cen-b2g/build/tools/profiler/libunwind/src/doc/unw_get_proc_info_by_ip.tex unw_get_proc_info_by_ip.man make: latex2man: Command not found make: *** [unw_get_proc_info_by_ip.man] Error 127 make: Leaving directory `/builds/slave/m-cen-b2g/build/obj-b2g/tools/profiler/libunwind/src/doc' make: *** [all-recursive] Error 1
this means that b2g is building with profiling enabled. Is that expected?
(In reply to Benoit Girard (:BenWa) from comment #1) > this means that b2g is building with profiling enabled. Is that expected? According to the mozconfig given to me by the b2g team, yes http://hg.mozilla.org/mozilla-central/file/default/b2g/config/mozconfigs/linux32/debug
libunwind itself does not support building without documentation, but we may be able to trick it somehow...
Created attachment 608471 [details] [diff] [review] Patch (v1) This is a hack, but I think not a very bad one, in that we don't need to modify libunwind at all. The way that this patch works is that it replaces the commands in the docs Makefile (the one in the objdir) with echo so that they won't do anything useful.