philip Sat Mar 15 13:30:06 2003 EDT
Modified files:
/phpdoc/en/faq build.xml
Log:
Add faq about the common my_tempnam warning. Closes bug #21029. In the
future, add diff of bundled vs non-bundled.
Index: phpdoc/en/faq/build.xml
diff -u phpdoc/en/faq/build.xml:1.23 phpdoc/en/faq/build.xml:1.24
--- phpdoc/en/faq/build.xml:1.23 Tue Feb 4 04:38:22 2003
+++ phpdoc/en/faq/build.xml Sat Mar 15 13:30:06 2003
@@ -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>
@@ -441,6 +441,29 @@
]]>
</programlisting>
If that spews out errors, you know your include files are messed up.
+ </para>
+ </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>
--
PHP Documentation Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
