Changes between Version 12 and Version 13 of CompileError

Timestamp:

2014-09-25T16:38:27Z (11 years ago)

Author:

zooko

Comment:

http → https

CompileError

@@ -33 +33 @@
 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 http://twistedmatrix.com/trac/ 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.
+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 https://twistedmatrix.com/trac/ 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.
 
-2. Second, if a "Python egg" of the library for your platform and your version of Python is available from the library's page on http://pypi.python.org or from [//source/tahoe-lafs/deps/tahoe-lafs-dep-eggs/README.html the collection of eggs hosted on https://tahoe-lafs.org], it will download and use that. In that case it will not attempt to compile the library at all. It will instead use the precompiled "egg" package of that library.
+2. Second, if a "Python egg" of the library for your platform and your version of Python is available from the library's page on https://pypi.python.org or from [//source/tahoe-lafs/deps/tahoe-lafs-dep-eggs/README.html the collection of eggs hosted on https://tahoe-lafs.org], it will download and use that. In that case it will not attempt to compile the library at all. It will instead use the precompiled "egg" package of that library.
 
 3. Third, only if both of the two methods above failed then it downloads the source code of the library and tries to compile it. If you have a working compiler and all the needed header files then the compilation will succeed.