[Lxml-checkins] r44198 - lxml/branch/lxml-1.3/doc

[scoder at codespeak.net]

Author: scoder
Date: Tue Jun 12 19:41:50 2007
New Revision: 44198

Modified:
   lxml/branch/lxml-1.3/doc/FAQ.txt
   lxml/branch/lxml-1.3/doc/build.txt
Log:
doc updates from trunk

Modified: lxml/branch/lxml-1.3/doc/FAQ.txt
==============================================================================
--- lxml/branch/lxml-1.3/doc/FAQ.txt	(original)
+++ lxml/branch/lxml-1.3/doc/FAQ.txt	Tue Jun 12 19:41:50 2007
@@ -253,7 +253,12 @@
 b) If you are using threads, please see the following section to check if
    you touch on one of the potential pitfalls.
 
-c) Otherwise, we would really like to hear about it.  Please report it to the
+c) Try to reproduce the problem with the latest versions of libxml2 and
+   libxslt.  From time to time, bugs and race conditions are found in these
+   libraries, so a more recent version might already contain a fix for your
+   problem.
+
+d) Otherwise, we would really like to hear about it.  Please report it to the
    `mailing list`_ so that we can fix it.  It is very helpful in this case if
    you can come up with a short code snippet that demonstrates your problem.
    Please also report the version of lxml, libxml2 and libxslt that you are

Modified: lxml/branch/lxml-1.3/doc/build.txt
==============================================================================
--- lxml/branch/lxml-1.3/doc/build.txt	(original)
+++ lxml/branch/lxml-1.3/doc/build.txt	Tue Jun 12 19:41:50 2007
@@ -44,7 +44,7 @@
   http://codespeak.net/svn/lxml/pyrex/
 
   A subversion checkout of lxml will automatically retrieve the latest Pyrex
-  as external project source (``svn:externals``).  Look out for the ``Pyrex``
+  as external project source (``svn:externals``).  Look for the ``Pyrex``
   directory in the source tree.
 
   Since version 1.1.2, the lxml source distribution also includes this Pyrex
@@ -182,6 +182,26 @@
 lxml maintainer.
 
 
+Providing newer library versions on Mac-OS X
+--------------------------------------------
+
+The Unix environment in Mac-OS X makes it relatively easy to install
+Unix/Linux style package management tools and new software.  However, it seems
+to be hard to get libraries set up for exclusive usage that Mac-OS X ships in
+an older version.  The result can be segfaults on this platform that are hard
+to track down.
+
+To make sure the newer libxml2 and libxslt versions are used (e.g. under
+fink), you should add the directory where you installed the libraries to the
+``DYLD_LIBRARY_PATH`` environment variable.  This seems to fix a lot of
+problems for users.
+
+Alternatively, you can build lxml statically.  A way to do this on MS Windows
+is described in the next section, but it should be easy to adapt it for
+Mac-OS.  That way, you can always be sure you use the versions you compiled
+lxml with, regardless of the runtime environement.
+
+
 Static linking on Windows
 -------------------------