From: Julian Ospald Date: Sat Aug 4 00:33:15 UTC 2012 Subject: devmanual document necessity to force all build logs verbose --- devmanual/ebuild-writing/common-mistakes/text.xml +++ devmanual/ebuild-writing/common-mistakes/text.xml @@ -57,6 +57,37 @@ +
+Build log not verbose + +When writing ebuilds you should always check the build log, because the build +system might ignore CC/CXX/LD/CFLAGS/LDFLAGS and such or add undesired flags +by default. In order to analyze this and have complete information in case +someone reports a bug for your package the build log must always be verbose. +

+There are several ways to fix non-verbose build logs depending on the build system: +

+

+For cmake based build systems it should be sufficient that the ebuild calls +cmake-utils_src_compile which picks up the cmake-utils.eclass variable 'CMAKE_VERBOSE=1' +by default. If you call emake directly for whatever reason you can do 'emake VERBOSE=1' +(note that cmake-utils_src_compile takes arguments as well which are passed to make). +

+ +

+For autotools based build systems portage already passes '--disable-silent-rules' +to econf. +

+ +

+For custom Makefiles you probably have to write a patch. Try to get upstream to include an +option like 'V=1' to enable full verbosity. +

+ If you notice non-verbose build log in any package open a bug and make it block the +tracker bug #429308 + +
+