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,32 @@
     <programlisting>CFLAGS+= -DHAVE_SOUND</programlisting>
   </sect1>
 
+  <sect1 xml:id="dads-verbose-logs">
+    <title>Verbose Build Logs</title>
+
+    <para>Make the port build system display all commands executed
+      during the build stage.  Complete build logs are crucial to
+      debugging port problems.</para>
+
+    <para>Non-informative build log example (bad):</para>
+
+    <programlisting>  CC     source1.o
+  CC     source2.o
+  CCLD   someprogram</programlisting>
+
+    <para>Verbose build log example (good):</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>Some build systems such as <application>CMake</application>,
+      <application>ninja</application>, and <application>GNU
+      configure</application> are set up for verbose logging by
+      the ports framework.  In other cases ports might need
+      individial tweaks.</para>
+  </sect1>
+
   <sect1 xml:id="dads-feedback">
     <title>Feedback</title>