Add faq about the common my_tempnam warning. Closes bug #21029. In the

future, add diff of bundled vs non-bundled.


git-svn-id: https://svn.php.net/repository/phpdoc/en/trunk@120344 c90b9560-bf6c-de11-be94-00142212c4b1

faq/build.xml

@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="iso-8859-1"?>
-<!-- $Revision: 1.23 $ -->
+<!-- $Revision: 1.24 $ -->
 <chapter id="faq.build">
   <title>Build Problems</title>
   <titleabbrev>Build Problems</titleabbrev>
@@ -445,6 +445,29 @@ $ gcc -E test.c >/dev/null
     </answer>
    </qandaentry>
    
+   <qandaentry id="faq.build.mysql.tempnam">
+    <question>
+     <para>
+      When compiling PHP with MySQL, configure runs fine but during
+      <literal>make</literal> I get an error similar to the following:
+      <emphasis>ext/mysql/libmysql/my_tempnam.o(.text+0x46): In function 
+      my_tempnam': /php4/ext/mysql/libmysql/my_tempnam.c:103: the 
+      use of tempnam' is dangerous, better use mkstemp'</emphasis>, 
+      what's wrong?
+     </para>
+    </question>
+    <answer>
+     <para>
+      First, it's important to realize that this is a <literal>
+      Warning</literal> and not a fatal error.  Because this is
+      often the last output seen during <literal>make</literal>,
+      it may seem like a fatal error but it's not.  Of course, if
+      you set your compiler to die on Warnings, it will.  Also
+      keep in mind that MySQL support is enabled by default.
+     </para>
+    </answer>
+   </qandaentry>
+   
    <qandaentry id="faq.build.upgrade">
     <question>
      <para>