From 96858e2581ba9fc17eacb407b66baf86d9509d9e Mon Sep 17 00:00:00 2001 From: davidsarah <> Date: Wed, 16 Jan 2013 21:15:18 +0000 Subject: [PATCH] trivial correction (Tahoe-LAFS also uses pure-Python libraries that don't need to be mentioned) [Imported from Trac: page CompileError, version 8] --- CompileError.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/CompileError.md b/CompileError.md index 2e3e330..33501a6 100644 --- a/CompileError.md +++ b/CompileError.md @@ -18,9 +18,9 @@ error: Python.h: No such file or directory ### Why This Happens -To decide what to do about this, you have to understand that the Tahoe-LAFS software itself is written in 100% pure Python and never gets compiled. However, Tahoe-LAFS uses several libraries which themselves contain native C or C++ code that needs to be compiled. Currently there are six libraries that Tahoe-LAFS uses: `Twisted`, `pyOpenSSL`, `pycrypto`, `pycryptopp`, `zfec`, and `zope.interface`. +To decide what to do about this, you have to understand that the Tahoe-LAFS software itself is written in 100% pure Python and never gets compiled. However, Tahoe-LAFS uses several libraries which themselves contain native C or C++ code that needs to be compiled. Currently there are six such libraries that Tahoe-LAFS uses: `Twisted`, `pyOpenSSL`, `pycrypto`, `pycryptopp`, `zfec`, and `zope.interface`. -To understand why the compile failure happens and how to get past it, you have to understand that `python setup.py build` tries *three* different methods of satisfying Tahoe-LAFS's need for its libraries, and only if all three methods fail does it emit an error message like this. +To understand why the compile failure happens and how to get past it, you have to understand that `python setup.py build` tries *three* different methods of satisfying Tahoe-LAFS' need for its libraries, and only if all three methods fail does it emit an error message like this. 1. First, if a suitable version of the library is already installed in your system, then Tahoe-LAFS will use it. So for example if the compile failure is happening because it can't compile `Twisted`, and if you were to install Twisted into your operating system — such as by running `sudo apt-get install python-twisted` on Debian, or by downloading and running the MSI installer for Twisted from on Windows — then the compile failure would stop happening, because it would no longer attempt to compile Twisted, because it would use the installed Twisted on your system instead. @@ -36,6 +36,6 @@ If you get an error message like this, then please look at [//source/tahoe-lafs/ If there are any blank cells in your row of the table, then that's your problem. The problem is that one of those dependencies is not available in precompiled binary form. To get this fixed, please send an email to [//cgi-bin/mailman/listinfo/tahoe-dev the tahoe-dev mailing list] requesting that someone who has your platform build a precompiled binary of that dependency for you. -### for Tahoe-LAFS developers and packagers +### For Tahoe-LAFS developers and packagers -See also [Packaging](Packaging), [OSPackages](OSPackages), [Manual](Manual), and [NewbieDeveloperSetup](NewbieDeveloperSetup) \ No newline at end of file +See also [Packaging](Packaging), [OSPackages](OSPackages), [Manual](Manual), and [NewbieDeveloperSetup](NewbieDeveloperSetup)