Index: en_US.ISO8859-1/books/porters-handbook/porting-dads/chapter.xml
===================================================================
--- en_US.ISO8859-1/books/porters-handbook/porting-dads/chapter.xml
+++ en_US.ISO8859-1/books/porters-handbook/porting-dads/chapter.xml
@@ -322,6 +322,33 @@
     <programlisting>CFLAGS+= -DHAVE_SOUND</programlisting>
   </sect1>
 
+  <sect1 xml:id="dads-verbose-logs">
+    <title>Verbose Build Logs</title>
+
+    <para>The port should always output as much information as
+      possible during the build, for build logs are crucial to
+      debugging port problems.  Some build systems hide executed
+      build commands and only display non-informative summary,
+      this behavior should be inhibited.</para>
+
+    <para>Non-informative build log example:</para>
+
+    <programlisting>  CC     source1.o
+  CC     source2.o
+  CCLD   someprogram</programlisting>
+
+    <para>Verbose build log example:</para>
+
+    <programlisting>cc -O2 -pipe -I/usr/local/include -c -o source1.o source1.c
+cc -O2 -pipe -I/usr/local/include -c -o source2.o source2.c
+cc -o someprogram source1.o source2.o -L/usr/local/lib -lsomelib</programlisting>
+
+    <para>For instance, for <varname>GNU_CONFIGURE</varname>-using
+      ports verbose logs may usually be enabled with</para>
+
+    <programlisting>CONFIGURE_ARGS+= --disable-silent-rules</programlisting>
+  </sect1>
+
   <sect1 xml:id="dads-feedback">
     <title>Feedback</title>