tahoe-lafs/trac-2024-07-25
2
0
Issues 1.1k Wiki Activity

edit for readability 

[Imported from Trac: page CompileError, version 9]
zooko 2013-04-03 12:29:15 +00:00
parent cad8e194c1
commit 5bd9d42f06
1 changed files with 1 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
CompileError.md

@ -18,7 +18,7 @@ error: Python.h: No such file or directory
### Why This Happens ### 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 such libraries that Tahoe-LAFS uses: `Twisted`, `pyOpenSSL`, `pycrypto`, `pycryptopp`, `zfec`, and `zope.interface`. First of all, 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' 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.