Changeset 101 for trunk/docs
- Timestamp:
- Apr 24, 2007, 10:57:49 AM (18 years ago)
- Location:
- trunk/docs
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
trunk/docs/Changelog
r100 r101 1 2.3.3: 1 2.3.4: 2 * fixed compilation of kern_head (problem reported by S. Clormann) 3 * more typos fixed (reported by John Horne) 4 5 2.3.3 (27-03-2007): 2 6 * fixed typos in configure.ac and manual (reported by John Horne) 3 7 * don't use mysql_options on x86_64, since libmysql is broken -
trunk/docs/FAQ.html
r91 r101 139 139 </ul> 140 140 </div> 141 <p><i>FAQ Revised: Monday 12 February 2007 23:06:43</i></p>141 <p><i>FAQ Revised: Saturday 14 April 2007 17:05:58</i></p> 142 142 <hr><h2>Table of Contents</h2> 143 143 <dl> … … 161 161 <li><a href="#Build and install8">2.9. What is sh_tiger1.s?</a></li> 162 162 <li><a href="#Build and install9">2.10. Why does static compiling (<code>--enable-static</code>) on MaxOS X fail ?</a></li> 163 <li><a href="#Build and install10">2.11. Why does compiling with MySQL fail on Solaris ?</a></li> 163 164 </ul></dd> 164 165 <dt><b>3. File checking</b></dt> … … 406 407 <a href="http://developer.apple.com/qa/qa2001/qa1118.html">Technical Q&A QA1118</a>. 407 408 This is a MacOS X issue and not a bug in samhain.<br><br></dd> 409 <dt><b><a name="Build and install10">2.11. Why does compiling with MySQL fail on Solaris ?</a></b></dt> 410 <dd>The reason is often the shell script 'mysql_config' that comes as part 411 of MySQL. This script is intended to print appropriate compiler flags for 412 compiling applications that use MySQL. Unfortunately, since Sun compiles 413 MySQL with the Solaris compiler, this script outputs options for the Solaris 414 compiler (i.e. unsuitable for gcc). To solve this problem, you need to move 415 this script (i.e. 'mysql_config') out of your PATH before running 416 <tt>./configure</tt> (unless of course you are using the Solaris compiler 417 rather than gcc).<br><br></dd> 408 418 </dl> 409 419 <hr><h2>3. File checking</h2> … … 469 479 as "localhost" to the server, thus the server 470 480 needs to trust the client name 471 as reported by the client itself, and suppress all er oors on resolving481 as reported by the client itself, and suppress all errors on resolving 472 482 this name to the apparent address. In the server configuration: 473 483 … … 587 597 <p> 588 598 Alternatively, you can <code>scp</code> the database 589 to the client, run <code>samhain -t update -l none</code> (you 599 to the client, run <code>samhain -t update -l none --foreground</code> 600 (you 590 601 need to avoid logging because otherwise you will get in conflict with 591 602 the running samhain daemon), and then <code>scp</code> the
Note:
See TracChangeset
for help on using the changeset viewer.