Changeset 5e8edab5 for general/prog
- Timestamp:
- 05/24/2019 02:26:17 AM (5 years ago)
- Branches:
- elogind
- Children:
- 8eebfaa5
- Parents:
- 215c728b
- Location:
- general/prog
- Files:
-
- 16 edited
Legend:
- Unmodified
- Added
- Removed
-
general/prog/dbus-python.xml
r215c728b r5e8edab5 118 118 <screen><userinput>mkdir python2 && 119 119 pushd python2 && 120 PYTHON=/usr/bin/python \120 PYTHON=/usr/bin/python2 \ 121 121 ../configure --prefix=/usr --docdir=/usr/share/doc/dbus-python-&dbus-python-version; && 122 122 make && -
general/prog/doxygen.xml
r215c728b r5e8edab5 150 150 </para> 151 151 152 <screen ><userinput>cmake -DDOC_INSTALL_DIR=share/doc/doxygen-&doxygen-version; -Dbuild_doc=ON .. &&152 <screen remap="doc"><userinput>cmake -DDOC_INSTALL_DIR=share/doc/doxygen-&doxygen-version; -Dbuild_doc=ON .. && 153 153 154 154 make docs</userinput></screen> -
general/prog/gdb.xml
r215c728b r5e8edab5 120 120 </para> 121 121 122 <screen ><userinput>make -C gdb/doc doxy</userinput></screen>122 <screen remap="doc"><userinput>make -C gdb/doc doxy</userinput></screen> 123 123 124 124 <para> … … 126 126 </para> 127 127 128 <screen ><userinput>pushd gdb/testsuite &&128 <screen remap="test"><userinput>pushd gdb/testsuite && 129 129 make site.exp && 130 130 echo "set gdb_test_timeout 120" >> site.exp && … … 205 205 </para> 206 206 207 <screen role="root"><userinput>install -d /usr/share/doc/gdb-&gdb-version; && 207 <screen role="root" 208 remap="doc"><userinput>install -d /usr/share/doc/gdb-&gdb-version; && 208 209 rm -rf gdb/doc/doxy/xml && 209 210 cp -Rv gdb/doc/doxy /usr/share/doc/gdb-&gdb-version;</userinput></screen> -
general/prog/git.xml
r215c728b r5e8edab5 165 165 </para> 166 166 167 <screen ><userinput>make html</userinput></screen>167 <screen remap="doc"><userinput>make html</userinput></screen> 168 168 169 169 <para> … … 172 172 </para> 173 173 174 <screen ><userinput>make man</userinput></screen>174 <screen remap="doc"><userinput>make man</userinput></screen> 175 175 176 176 <para> … … 195 195 </para> 196 196 197 <screen role="root" ><userinput>make install-man</userinput></screen>197 <screen role="root" remap="doc"><userinput>make install-man</userinput></screen> 198 198 199 199 <para> … … 202 202 </para> 203 203 204 <screen role="root" ><userinput>make htmldir=/usr/share/doc/git-&git-version; install-html</userinput></screen>204 <screen role="root" remap="doc"><userinput>make htmldir=/usr/share/doc/git-&git-version; install-html</userinput></screen> 205 205 206 206 <!-- ==== Method 2 for docs ====== --> -
general/prog/jinja2.xml
r215c728b r5e8edab5 97 97 </para> 98 98 99 <screen role="root"><userinput>python setup.py install --optimize=1</userinput></screen>99 <screen role="root"><userinput>python2 setup.py install --optimize=1</userinput></screen> 100 100 101 101 <para> -
general/prog/libxml2py2.xml
r215c728b r5e8edab5 99 99 100 100 <screen><userinput>cd python && 101 python setup.py build</userinput></screen>101 python2 setup.py build</userinput></screen> 102 102 103 103 <para> … … 107 107 </para> 108 108 109 <screen role="root"><userinput>python setup.py install --optimize=1</userinput></screen>109 <screen role="root"><userinput>python2 setup.py install --optimize=1</userinput></screen> 110 110 111 111 </sect3> -
general/prog/llvm.xml
r215c728b r5e8edab5 211 211 212 212 <para> 213 If you have installed <application>Sphinx</application> and 214 <application>recommonmark</application> and wish 215 to generate the html documentation and manual pages, issue the following 216 commands: 217 </para> 218 219 <screen remap="doc"><userinput>cmake -DLLVM_ENABLE_SPHINX=ON \ 220 -DSPHINX_WARNINGS_AS_ERRORS=OFF \ 221 -Wno-dev -G Ninja .. && 222 ninja docs-llvm-html docs-llvm-man</userinput></screen> 223 224 <para> 225 If you have downloaded the optional packages, the clang documentation 226 can be built too: 227 </para> 228 229 <screen remap="doc"><userinput>ninja docs-clang-html docs-clang-man</userinput></screen> 230 231 <para> 213 232 <!-- EDITORS - if you have more than 4 cores, take some offline to measure 214 233 the elapsed time for the tests. Also, libstdc++.a and perhaps libstdc++fs.a … … 234 253 235 254 <para> 236 If you have installed <application>Sphinx</application> and 237 <application>recommonmark</application> and wish 238 to generate the html documentation and manual pages, issue the following 239 commands: 240 </para> 241 <screen><userinput>cmake -DLLVM_ENABLE_SPHINX=ON \ 242 -DSPHINX_WARNINGS_AS_ERRORS=OFF \ 243 -Wno-dev -G Ninja .. && 244 ninja docs-llvm-html docs-llvm-man</userinput></screen> 245 <para> 246 If you have downloaded the optional packages, the clang documentation 247 can be built too: 248 </para> 249 <screen><userinput>ninja docs-clang-html docs-clang-man</userinput></screen> 250 251 <para> 252 Install the llvm documentation by running the following command as the 253 <systemitem class="username">root</systemitem> user: 254 </para> 255 256 <screen role="root"><userinput>install -v -m644 docs/man/* /usr/share/man/man1 && 255 If you have built the the llvm documentation, install it by running the 256 following commands as the <systemitem class="username">root</systemitem> 257 user: 258 </para> 259 260 <screen role="root" 261 remap="doc"><userinput>install -v -m644 docs/man/* /usr/share/man/man1 && 257 262 install -v -d -m755 /usr/share/doc/llvm-&llvm-version;/llvm-html && 258 263 cp -Rv docs/html/* /usr/share/doc/llvm-&llvm-version;/llvm-html</userinput></screen> 259 264 260 265 <para> 261 The clang documentation can be installed in the same way (again as the 266 If you have built the clang documentation, it can be installed in the 267 same way (again as the 262 268 <systemitem class="username">root</systemitem> user): 263 269 </para> 264 270 265 <screen role="root"><userinput>install -v -m644 tools/clang/docs/man/* /usr/share/man/man1 && 271 <screen role="root" 272 remap="doc"><userinput>install -v -m644 tools/clang/docs/man/* /usr/share/man/man1 && 266 273 install -v -d -m755 /usr/share/doc/llvm-&llvm-version;/clang-html && 267 274 cp -Rv tools/clang/docs/html/* /usr/share/doc/llvm-&llvm-version;/clang-html</userinput></screen> -
general/prog/lxml.xml
r215c728b r5e8edab5 105 105 106 106 <para> 107 To build the <application>Python 2</application> module, run: 107 To build both <application>Python 2</application> and 108 <application>Python 3</application> modules, run: 108 109 </para> 109 110 110 <screen><userinput>python setup.py build</userinput></screen> 111 <screen><userinput>python2 setup.py build && 112 python3 setup.py build</userinput></screen> 111 113 112 114 <para> 113 If you wish to run the tests, enter: <command>make test</command>. 115 If you wish to run the tests, enter: 116 <command>make PYTHON=python2 test</command> and 117 <command>make PYTHON=python3 test</command>. 114 118 This will rebuild the package for inplace use before running the tests. 115 119 One or more tests sometimes fail. … … 117 121 118 122 <para> 119 To install the <application>Python 2</application> module, 120 as the 121 <systemitem class="username">root</systemitem> user run: 123 To install both modules, issue the following commands as the 124 <systemitem class="username">root</systemitem> user: 122 125 </para> 123 126 124 <screen role="root"><userinput>python setup.py install --optimize=1</userinput></screen> 125 126 <para> 127 To build the <application>Python 3</application> module, run: 128 </para> 129 130 <screen><userinput>python3 setup.py clean && 131 python3 setup.py build</userinput></screen> 132 133 <para> 134 If you wish to run the tests, enter: <command>make PYTHON=python3 135 test</command>. This will rebuild the package for inplace use before 136 running the tests. One or more tests sometimes fail. 137 </para> 138 139 <para> 140 To install the <application>Python 3</application> module, 141 as the 142 <systemitem class="username">root</systemitem> user run: 143 </para> 144 145 <screen role="root"><userinput>python3 setup.py install --optimize=1</userinput></screen> 127 <screen role="root"><userinput>python2 setup.py install --optimize=1 && 128 python3 setup.py install --optimize=1</userinput></screen> 146 129 147 130 </sect3> -
general/prog/mako.xml
r215c728b r5e8edab5 99 99 </para> 100 100 101 <screen role="root"><userinput>python setup.py install - -optimize=1</userinput></screen>101 <screen role="root"><userinput>python2 setup.py install - -optimize=1</userinput></screen> 102 102 --> 103 103 <para> -
general/prog/mercurial.xml
r215c728b r5e8edab5 100 100 issue:</para> 101 101 102 <screen ><userinput>sed -i '/runrst/s/N)/N)3/' doc/Makefile &&102 <screen remap="doc"><userinput>sed -i '/runrst/s/N)/N)3/' doc/Makefile && 103 103 2to3-3.7 -w doc/hgmanpage.py && 104 104 make doc</userinput></screen> … … 111 111 issue:</para> 112 112 113 <screen ><userinput>cat > tests/blacklists/failed-tests << "EOF"113 <screen remap="test"><userinput>cat > tests/blacklists/failed-tests << "EOF" 114 114 <literal># Test Failures 115 115 test-gpg.t</literal> … … 119 119 To run the test suite, issue: 120 120 </para> 121 <screen ><userinput>rm -rf tests/tmp &&121 <screen remap="test"><userinput>rm -rf tests/tmp && 122 122 TESTFLAGS="-j<replaceable><N></replaceable> --tmpdir tmp --blacklist blacklists/failed-tests" make check</userinput></screen> 123 123 … … 130 130 the tests that failed before:</para> 131 131 132 <screen ><userinput>pushd tests &&132 <screen remap="test"><userinput>pushd tests && 133 133 rm -rf tmp && 134 134 ./run-tests.py --tmpdir tmp test-gpg.t … … 142 142 or not. One test, test-https.t, is known to fail.</para> 143 143 144 <para>An interesting switch is "- 144 <para>An interesting switch is "--time", which will generate at the end of 145 145 the test suite execution, a table with all executed tests and respective 146 146 start, end, user, system and real times. Notice that the switches may be … … 156 156 command (as <systemitem class="username">root</systemitem>):</para> 157 157 158 <screen role="root"><userinput>make PREFIX=/usr install-doc</userinput></screen> 158 <screen role="root" 159 remap="doc"><userinput>make PREFIX=/usr install-doc</userinput></screen> 159 160 160 161 <para>After installed, two very quick and simple tests should run correctly. -
general/prog/pycairo.xml
r215c728b r5e8edab5 95 95 96 96 <para> 97 Install <application>PyCairo</application> for Python2 by running98 the following commands:97 Install <application>PyCairo</application> for Python2 and Python3 by 98 running the following commands: 99 99 </para> 100 100 101 <screen><userinput>python2 setup.py build</userinput></screen> 101 <screen><userinput>python2 setup.py build && 102 python3 setup.py build</userinput></screen> 102 103 103 104 <para> … … 109 110 </para> 110 111 111 <screen role="root"><userinput>python2 setup.py install --optimize=1 && 112 <screen role="root"><userinput>python2 setup.py install --optimize=1 && 113 python3 setup.py install --optimize=1</userinput></screen> 114 <!-- Seems that install does the following too 112 115 python2 setup.py install_pycairo_header && 113 python2 setup.py install_pkgconfig</userinput></screen> 114 115 <para> 116 Install <application>PyCairo</application> for Python3 by running 117 the following commands: 118 </para> 119 120 <screen><userinput>python3 setup.py build</userinput></screen> 121 122 <para> 123 This package does not come with a test suite. 124 </para> 125 126 <para> 127 Now, as the <systemitem class="username">root</systemitem> user: 128 </para> 129 130 <screen role="root"><userinput>python3 setup.py install --optimize=1 && 131 python3 setup.py install_pycairo_header && 132 python3 setup.py install_pkgconfig</userinput></screen> 116 python2 setup.py install_pkgconfig</userinput></screen>--> 133 117 134 118 </sect3> -
general/prog/pycrypto.xml
r215c728b r5e8edab5 93 93 94 94 <para> 95 To build the <application>Python 2</application> module,96 run the following command:95 To build the <application>Python 2</application> and 96 <application>Python 3</application> modules, run the following commands: 97 97 </para> 98 98 99 <screen><userinput>python setup.py build</userinput></screen> 99 <screen><userinput>python2 setup.py build && 100 python3 setup.py build</userinput></screen> 100 101 101 102 <para> 102 To install the <application>Python 2</application> module, 103 run the following command as the 103 To install both modules, run the following commands as the 104 104 <systemitem class="username">root</systemitem> user: 105 105 </para> 106 106 107 <screen role="root"><userinput>python setup.py install --optimize=1</userinput></screen> 108 109 <para> 110 To build the <application>Python 3</application> module, 111 run the following command: 112 </para> 113 114 <screen><userinput>python3 setup.py build</userinput></screen> 115 116 <para> 117 To install the <application>Python 3</application> module, 118 run the following command as the 119 <systemitem class="username">root</systemitem> user: 120 </para> 121 122 <screen role="root"><userinput>python3 setup.py install --optimize=1</userinput></screen> 107 <screen role="root"><userinput>python2 setup.py install --optimize=1 && 108 python3 setup.py install --optimize=1</userinput></screen> 123 109 124 110 </sect3> … … 137 123 </seg> 138 124 <seg> 139 pycrypto-&pycrypto-version;-py 2.7.egg-info and/or140 pycrypto-&pycrypto-version;-py 3.6.egg-info125 pycrypto-&pycrypto-version;-py&python2-majorver;.egg-info and/or 126 pycrypto-&pycrypto-version;-py&python3-majorver;.egg-info 141 127 </seg> 142 128 <seg> -
general/prog/pyyaml.xml
r215c728b r5e8edab5 97 97 98 98 <para> 99 To build the <application>Python 2</application> module, 100 run the following command: 99 To build both <application>Python 2</application> and 100 <application>Python 3</application> modules, 101 run the following commands: 101 102 </para> 102 103 103 <screen><userinput>python setup.py build</userinput></screen> 104 <screen><userinput>python2 setup.py build && 105 python3 setup.py build</userinput></screen> 104 106 105 107 <para> 106 To install the <application>Python 2</application> module, 107 run the following command as the 108 To install both modules, run the following commands as the 108 109 <systemitem class="username">root</systemitem> user: 109 110 </para> 110 111 111 <screen role="root"><userinput>python setup.py install --optimize=1</userinput></screen> 112 113 <para> 114 To build the <application>Python 3</application> module, 115 run the following command: 116 </para> 117 118 <screen><userinput>python3 setup.py build</userinput></screen> 119 120 <para> 121 To install the <application>Python 3</application> module, 122 run the following command as the 123 <systemitem class="username">root</systemitem> user: 124 </para> 125 126 <screen role="root"><userinput>python3 setup.py install --optimize=1</userinput></screen> 112 <screen role="root"><userinput>python2 setup.py install --optimize=1 && 113 python3 setup.py install --optimize=1</userinput></screen> 127 114 128 115 </sect3> -
general/prog/rust.xml
r215c728b r5e8edab5 185 185 <para role="optional"> 186 186 <xref linkend="gdb"/> (used by the testsuite if it is present) and 187 <xref linkend="python2"/> (if gdb is present, it must have been built 188 with Python 2 support to prevent some tests failing. Furthermore, another 189 test fails if Python 2 is not present) 187 <xref linkend="python2"/> (one test fails if Python 2 is not present) 190 188 </para> 191 189 … … 301 299 which need Thumb (ARM) compilers will fail, all in <filename 302 300 class="directory">ui/issues</filename> for issues 37131, 49851 and 50993. 303 Occasionallya fourth test,301 If <xref linkend="python2"/> is not installed, a fourth test, 304 302 <filename>run-make-fulldeps/sysroot-crates-are-unstable</filename> 305 303 fails. If gdb has been installed, in some circumstances three tests in -
general/prog/scour.xml
r215c728b r5e8edab5 107 107 108 108 <para> 109 To build the <application>Python 2</application> module, 110 run the following command: 109 To build both <application>Python 2</application> and 110 <application>Python 3</application> modules, 111 run the following commands: 111 112 </para> 112 113 113 <screen><userinput>python setup.py build</userinput></screen> 114 <screen><userinput>python2 setup.py build && 115 python3 setup.py build</userinput></screen> 114 116 115 117 <para> 116 To partially test the results, issue: <command>python testcss.py</command>.118 To partially test the results, issue: <command>python2 testcss.py</command>. 117 119 If you have installed <application>Six</application> you can run the main 118 tests by issuing: <command>python testscour.py</command>.120 tests by issuing: <command>python2 testscour.py</command>. 119 121 </para> 120 122 121 123 <para> 122 To install the <application>Python 2</application> module 123 run the following command as the 124 To install both modules, run the following command as the 124 125 <systemitem class="username">root</systemitem> user: 125 126 </para> 126 127 127 <screen role="root"><userinput>python setup.py install --optimize=1</userinput></screen> 128 129 <para> 130 To build the <application>Python 3</application> module, 131 run the following command: 132 </para> 133 134 <screen><userinput>python3 setup.py build</userinput></screen> 135 136 <para> 137 To install the <application>Python 3</application> module, 138 run the following command as the 139 <systemitem class="username">root</systemitem> user: 140 </para> 141 142 <screen role="root"><userinput>python3 setup.py install --optimize=1</userinput></screen> 128 <screen role="root"><userinput>python2 setup.py install --optimize=1 && 129 python3 setup.py install --optimize=1</userinput></screen> 143 130 144 131 </sect3> -
general/prog/six.xml
r215c728b r5e8edab5 90 90 91 91 <para> 92 Install <application>six</application> for Python 2 by running93 the following commands:92 Install <application>six</application> for Python 2 and Python 3 93 by running the following commands: 94 94 </para> 95 95 96 <screen><userinput>python2 setup.py build</userinput></screen> 96 <screen><userinput>python2 setup.py build && 97 python3 setup.py build</userinput></screen> 97 98 98 99 <para> … … 104 105 </para> 105 106 106 <screen role="root"><userinput>python2 setup.py install --optimize=1</userinput></screen> 107 108 <para> 109 Install <application>six</application> for Python3 by running 110 the following commands: 111 </para> 112 113 <screen><userinput>python3 setup.py build</userinput></screen> 114 115 <para> 116 This package does not come with a test suite. 117 </para> 118 119 <para> 120 Now, as the <systemitem class="username">root</systemitem> user: 121 </para> 122 123 <screen role="root"><userinput>python3 setup.py install --optimize=1</userinput></screen> 107 <screen role="root"><userinput>python2 setup.py install --optimize=1 && 108 python3 setup.py install --optimize=1</userinput></screen> 124 109 125 110 </sect3>
Note:
See TracChangeset
for help on using the changeset viewer.