FAQ.rst		FAQ.rst
	skipping to change at line 22		skipping to change at line 22
	mysqlclient_r is the thread-safe library. It's not available on		mysqlclient_r is the thread-safe library. It's not available on
	all platforms, or all installations, apparently. You'll need to		all platforms, or all installations, apparently. You'll need to
	reconfigure site.cfg (in MySQLdb-1.2.1 and newer) to have		reconfigure site.cfg (in MySQLdb-1.2.1 and newer) to have
	threadsafe = False.		threadsafe = False.
	mysql.h: No such file or directory		mysql.h: No such file or directory
	This almost always mean you don't have development packages		This almost always mean you don't have development packages
	installed. On some systems, C headers for various things (like MySQL)		installed. On some systems, C headers for various things (like MySQL)
	are distributed as a seperate package. You'll need to figure out		are distributed as a separate package. You'll need to figure out
	what that is and install it, but often the name ends with -devel.		what that is and install it, but often the name ends with -devel.
	Another possibility: Some older versions of mysql_config behave oddly		Another possibility: Some older versions of mysql_config behave oddly
	and may throw quotes around some of the path names, which confused		and may throw quotes around some of the path names, which confused
	MySQLdb-1.2.0. 1.2.1 works around these problems. If you see things		MySQLdb-1.2.0. 1.2.1 works around these problems. If you see things
	like -I'/usr/local/include/mysql' in your compile command, that's		like -I'/usr/local/include/mysql' in your compile command, that's
	probably the issue, but it shouldn't happen any more.		probably the issue, but it shouldn't happen any more.
	ImportError		ImportError
	-----------		-----------
	skipping to change at line 71		skipping to change at line 71
	Solutions:		Solutions:
	* set the LD_LIBRARY_PATH environment variable so that it includes		* set the LD_LIBRARY_PATH environment variable so that it includes
	the path to the MySQL libraries.		the path to the MySQL libraries.
	* set static=True in site.cfg for static linking		* set static=True in site.cfg for static linking
	* reconfigure your system so that the MySQL libraries are on the		* reconfigure your system so that the MySQL libraries are on the
	default loader path. In Linux, you edit /etc/ld.so.conf and run		default loader path. In Linux, you edit /etc/ld.so.conf and run
	ldconfig. For Solaris, see `Linker and Libraries Guide		ldconfig. For Solaris, see `Linker and Libraries Guide
	<http://docs.sun.com/app/docs/doc/817-3677/6mj8mbtbe?a=view>`_.		<http://docs.oracle.com/cd/E19253-01/817-1984/chapter6-63352/>`_.
	ImportError: ld.so.1: python: fatal: libmtmalloc.so.1: DF_1_NOOPEN tagged object may not be dlopen()'ed		ImportError: ld.so.1: python: fatal: libmtmalloc.so.1: DF_1_NOOPEN tagged object may not be dlopen()'ed
	This is a weird one from Solaris. What does it mean? I have no idea.		This is a weird one from Solaris. What does it mean? I have no idea.
	However, things like this can happen if there is some sort of a compiler		However, things like this can happen if there is some sort of a compiler
	or environment mismatch between Python and MySQL. For example, on some		or environment mismatch between Python and MySQL. For example, on some
	commercial systems, you might have some code compiled with their own		commercial systems, you might have some code compiled with their own
	compiler, and other things compiled with GCC. They don't always mesh		compiler, and other things compiled with GCC. They don't always mesh
	together. One way to encounter this is by getting binary packages from		together. One way to encounter this is by getting binary packages from
	different vendors.		different vendors.
End of changes. 2 change blocks.
	2 lines changed or deleted		2 lines changed or added
This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/