Changeset 5101276
- Timestamp:
- 06/16/2016 04:23:22 PM (7 years ago)
- Branches:
- 10.0, 10.1, 11.0, 11.1, 11.2, 11.3, 12.0, 7.10, 8.0, 8.1, 8.2, 8.3, 8.4, 9.0, 9.1, basic, bdubbs/svn, elogind, kea, ken/inkscape-core-mods, lazarus, lxqt, nosym, perl-modules, plabs/python-mods, qt5new, trunk, upgradedb, xry111/intltool, xry111/soup3, xry111/test-20220226, xry111/xf86-video-removal
- Children:
- 2086c106
- Parents:
- 2e15af7
- Files:
-
- 3 edited
Legend:
- Unmodified
- Added
- Removed
-
general/prog/swig.xml
r2e15af7 r5101276 7 7 <!ENTITY swig-download-http "&sourceforge-repo;/swig/swig-&swig-version;.tar.gz"> 8 8 <!ENTITY swig-download-ftp " "> 9 <!ENTITY swig-md5sum " 4bc5f46a6cdedbd8f579b25fafc96fd6">9 <!ENTITY swig-md5sum "bb4ab8047159469add7d00910e203124"> 10 10 <!ENTITY swig-size "7.6 MB"> 11 <!ENTITY swig-buildsize "9 3MB (1.1 GB with tests)">11 <!ENTITY swig-buildsize "94 MB (1.1 GB with tests)"> 12 12 <!ENTITY swig-time "0.4 SBU (25 SBU for the tests)"> 13 13 ]> … … 127 127 128 128 <para> 129 To test the results, issue: <command>make -k check</command>. Tests for 130 many languages are executed, depending on which ones you have installed. 131 Therefore, disk space and SBU values for the tests should be considered 132 only indications of necessary space and time, but not even approximated 133 values should they be considered. If you have both <xref 134 linkend="python2"/> and <xref linkend="python3"/> installed, the 135 Python-3 tests are not run. You can run tests for Python-3 by issuing 129 To test the results, issue: 130 <command>make -k check TCL_INCLUDE= GOGCC=true</command>. The (un)setting 131 of the two variables <envar>GOGCC</envar> and <envar>TCL_INCLUDE</envar> 132 is necessary, since they are not correctly set by 133 <emphasis>configure</emphasis>. The tests are only executed for the 134 languages installed on your machine, so the disk space and SBU values 135 given for the tests may vary, and should be considered as mere orders of 136 magnitude. If you have both <xref linkend="python2"/> and 137 <xref linkend="python3"/> installed, the Python-3 tests are not run. 138 You can run tests for Python-3 by issuing 136 139 <command>PY3=1 make check-python-examples</command> followed by 137 140 <command>PY3=1 make check-python-test-suite</command>. According to … … 149 152 </sect2> 150 153 151 <!--Optional section-->152 154 <sect2 role="commands"> 153 155 <title>Command Explanations</title> … … 166 168 SWIG implementation is very incomplete and a lot of tests fail. 167 169 </para> 170 168 171 </sect2> 169 172 … … 185 188 <seg> 186 189 /usr/share/doc/swig-&swig-version; and 187 /usr/share/swig /&swig-version;190 /usr/share/swig 188 191 </seg> 189 192 </seglistitem> … … 194 197 <?dbfo list-presentation="list"?> 195 198 <?dbhtml list-presentation="table"?> 196 197 <!-- If the program or library name conflicts (is the same) as the198 package name, add -prog or -lib to the varlistentry entity id199 and the 2nd entry of the indexterm zone entity -->200 199 201 200 <varlistentry id="swig-prog"> -
introduction/welcome/changelog.xml
r2e15af7 r5101276 47 47 <para>June 16th, 2016</para> 48 48 <itemizedlist> 49 <listitem> 50 <para>[pierre] - Update to SWIG-3.0.10. Fixes 51 <ulink url="&blfs-ticket-root;7924">#7924</ulink>.</para> 52 </listitem> 49 53 <listitem> 50 54 <para>[ken] - Reinstate build command for firefox which I accidentally -
packages.ent
r2e15af7 r5101276 302 302 <!ENTITY slang-version "2.2.4"> 303 303 <!ENTITY subversion-version "1.9.4"> 304 <!ENTITY swig-version "3.0. 9">304 <!ENTITY swig-version "3.0.10"> 305 305 <!ENTITY tcl-version "8.6.5"> 306 306 <!ENTITY tk-version "8.6.5">
Note:
See TracChangeset
for help on using the changeset viewer.