Changeset 3aee187 for general


Ignore:
Timestamp:
05/29/2020 09:43:04 AM (4 years ago)
Author:
Thomas Trepl <thomas@…>
Branches:
10.0, 10.1, 11.0, 11.1, 11.2, 11.3, 12.0, 12.1, kea, ken/TL2024, ken/inkscape-core-mods, ken/tuningfonts, lazarus, lxqt, plabs/newcss, plabs/python-mods, python3.11, qt5new, rahul/power-profiles-daemon, renodr/vulkan-addition, trunk, upgradedb, xry111/intltool, xry111/llvm18, xry111/soup3, xry111/test-20220226, xry111/xf86-video-removal
Children:
432f6a2
Parents:
26cceda
Message:

Upgrade subversion-1.14.0; add py3c

git-svn-id: svn://svn.linuxfromscratch.org/BLFS/trunk/BOOK@23213 af4574ff-66df-0310-9fd7-8a98e5e911e0

Location:
general/prog
Files:
1 added
3 edited

Legend:

Unmodified
Added
Removed
  • general/prog/python-modules.xml

    r26cceda r3aee187  
    4747      <listitem>
    4848        <para>
     49          <xref linkend="py3c"/>
     50        </para>
     51      </listitem>
     52      <listitem>
     53        <para>
    4954          <xref linkend="pyatspi2"/>
    5055        </para>
     
    163168
    164169  <xi:include xmlns:xi="http://www.w3.org/2001/XInclude"
     170    href="py3c.xml"/>
     171
     172  <xi:include xmlns:xi="http://www.w3.org/2001/XInclude"
    165173    href="pyatspi2.xml"/>
    166174<!--
  • general/prog/subversion.xml

    r26cceda r3aee187  
    129129      <xref linkend="libsecret"/>,
    130130<!--      <xref linkend="kdelibs"/> (for <ulink url="http://utils.kde.org/projects/kwalletmanager/">KWallet</ulink> support), -->
     131      <xref linkend="py3c"/> (for tests)
    131132      <xref linkend="python2"/> (with sqlite support for the tests),
    132133      <xref linkend="ruby"/>,
     
    141142      <ulink url="http://www.inet.no/dante/">Dante</ulink> or
    142143      <ulink url="http://jikes.sourceforge.net/">Jikes</ulink>,
    143       and <ulink url="https://junit.org/junit4/">JUnit 4</ulink>
    144       (to test the Java bindings). Note that JUnit is included with
     144      <ulink url="https://junit.org/junit4/">JUnit 4</ulink> (to test the Java bindings) and
    145145      <xref linkend="apache-ant"/>.
    146146    </para>
     
    197197
    198198    <para>
    199       If you passed the <option>--enable-javahl</option> parameter to
    200       <command>configure</command> and wish to build the Java bindings, issue
    201       the following command:
     199      If you wish to build the Java bindings pass the <option>--enable-javahl</option>
     200      parameter to the <command>configure</command> command. In addition, if
     201      you want to run the Java test suite, you have to specify the location
     202      of the <application>JUnit</application> file by adding
     203      <option>--with-junit=&lt;path to junit jar&gt;</option> (for
     204      instance <option>--with-junit=/usr/local/java/lib/junit-4.13.jar</option>)
     205      to <command>configure</command>. The JUnit jar file is no longer
     206      included in <xref linkend="apache-ant"/> and must be downloaded seperatly.
     207      To build the Java bindings, issue the following command:
    202208    </para>
    203209    <para>
     
    207213    <para>
    208214      If you want to compile <application>Perl</application>,
    209       <application>Python2</application>, or <application>Ruby</application>
     215      <application>Python</application>, or <application>Ruby</application>
    210216      bindings, issue any of the following command:
    211217    </para>
     
    213219      <screen><command>make swig-pl</command> # for <application>Perl</application>
    214220<command>make swig-py \
    215      swig_pydir=/usr/lib/python&python2-majorver;/site-packages/libsvn \
    216      swig_pydir_extra=/usr/lib/python&python2-majorver;/site-packages/svn</command> # for <application>Python</application>
     221     swig_pydir=/usr/lib/python&python3-majorver;/site-packages/libsvn \
     222     swig_pydir_extra=/usr/lib/python&python3-majorver;/site-packages/svn</command> # for <application>Python</application>
    217223<command>make swig-rb</command> # for <application>Ruby</application></screen>
    218224    </para>
     
    225231    <para>
    226232      To test the results of the Java bindings build,
    227       issue <command>make check-javahl</command>. The
    228       <application>JUnit</application> testing framework must be installed,
     233      issue <command>LANG=C make check-javahl</command>.
     234      <!-- ~~ This explanation is added to the configure above ~~
     235      The <application>JUnit</application> testing framework must be installed,
    229236      and the location of the JUnit jar has to be specified by passing the
    230       <option>--with-junit=&lt;path to junit jar&gt;</option> parameter to
     237      <option>- -with-junit=&lt;path to junit jar&gt;</option> parameter to
    231238      <command>configure</command>. Note that <application>JUnit</application>
    232239      is included in <xref linkend="apache-ant"/>, and can be accessed by
    233       passing <option>--with-junit=/opt/ant/lib/junit-4.12.jar</option>
     240      passing <option>- -with-junit=/opt/ant/lib/junit-4.12.jar</option>
    234241      to <command>configure</command>.
     242      -->
    235243    </para>
    236244
     
    242250      <command>make check-swig-rb</command>.
    243251    </para>
    244     <!-- I can no longer confirm this with 9.0-rc1 -renodr
    245     <note><para>
    246       The Python Bindings test suite (<command>make check-swig-py</command>)
    247       is broken with SWIG-4.0.0, however the bindings themselves work as
    248       expected.
    249     </para></note>
    250     -->
    251252
    252253    <para>
     
    269270    <para>
    270271      If you built the <application>Perl</application>,
    271       <application>Python2</application>, or
     272      <application>Python</application>, or
    272273      <application>Ruby</application> bindings, issue any of the following
    273274      commands as the <systemitem class="username">root</systemitem> user
     
    277278<screen><command>make install-swig-pl</command>
    278279<command>make install-swig-py \
    279       swig_pydir=/usr/lib/python&python2-majorver;/site-packages/libsvn \
    280       swig_pydir_extra=/usr/lib/python&python2-majorver;/site-packages/svn</command>
     280      swig_pydir=/usr/lib/python&python3-majorver;/site-packages/libsvn \
     281      swig_pydir_extra=/usr/lib/python&python3-majorver;/site-packages/svn</command>
    281282<command>make install-swig-rb</command></screen>
    282283    </para>
     
    386387          /usr/include/subversion-1,
    387388          /usr/lib/perl5/site_perl/&lfs-perl-version;/{,auto/}SVN,
    388           /usr/lib/python2.7/site-packages/{libsvn,svn},
     389          /usr/lib/python&python3-majorver;/site-packages/{libsvn,svn},
    389390          /usr/lib/ruby/site_ruby/&lt;x.y.z&gt;/{,&lt;arch-linux&gt;-linux/}svn,
    390391          /usr/lib/svn-javahl, and
  • general/prog/swig.xml

    r26cceda r3aee187  
    128128
    129129    <para>
    130       To test the results, issue: <command>make -k check TCL_INCLUDE=</command>.
     130      To test the results, issue: <command>PY3=1 make -k check TCL_INCLUDE=</command>.
    131131      The unsetting of the variable <envar>TCL_INCLUDE</envar> is
    132132      necessary since it is not correctly set by
     
    134134      languages installed on your machine, so the disk space and SBU values
    135135      given for the tests may vary, and should be considered as mere orders of
    136       magnitude. If you have <xref linkend="python2"/> installed, the Python-3
     136      magnitude. <!-- Phase out P2 support
     137      If you have <xref linkend="python2"/> installed, the Python-3
    137138      tests are not run.  You can run tests for Python-3 by issuing
    138139      <command>PY3=1 make check-python-examples</command> followed by
    139       <command>PY3=1 make check-python-test-suite</command>. According to
     140      <command>PY3=1 make check-python-test-suite</command>. --> According to
    140141      <application>SWIG</application>'s documentation, the failure of some
    141142      tests should not be considered harmful.
Note: See TracChangeset for help on using the changeset viewer.