Author: ken
Date: Sun Jan 6 17:30:32 2019
New Revision: 20927
Log:
Use python2 to build rustc.
Modified:
trunk/BOOK/general/prog/rust.xml
trunk/BOOK/introduction/welcome/changelog.xml
Modified: trunk/BOOK/general/prog/rust.xml
==============================================================================
--- trunk/BOOK/general/prog/rust.xml Sun Jan 6 15:15:46 2019 (r20926)
+++ trunk/BOOK/general/prog/rust.xml Sun Jan 6 17:30:32 2019 (r20927)
@@ -57,8 +57,7 @@
<para>
Rustc defaults to building for ALL supported architectures, using a
shipped copy of LLVM. In BLFS the build is only for the X86
architecture.
- Rustc still claims to require Python2, but that is only really
necessary
- when building some other architectures with the shipped LLVM. If you
+ If you
intend to develop rust crates, this build may not be good enough for
your
purposes.
</para>
@@ -119,8 +118,8 @@
<para role="required">
<xref linkend="curl"/>,
<xref linkend="cmake"/>,
- <xref linkend="libssh2"/>
-<!-- <xref linkend="python2"/> -->
+ <xref linkend="libssh2"/>, and
+ <xref linkend="python2"/>
</para>
<bridgehead renderas="sect4">Recommended</bridgehead>
@@ -194,7 +193,7 @@
</para>
<screen><userinput>export RUSTFLAGS="$RUSTFLAGS -C link-args=-lffi" &&
-python3 ./x.py build</userinput></screen>
+./x.py build</userinput></screen>
<para>
The build will report it failed to compile <filename>miri</filename>
@@ -205,8 +204,8 @@
<caution>
<para>
On AMD Ryzen processors (family 17h), the non-optimized version of
libstd
- which is compiled at the start of the tests contains two opcodes which
are
- not implemented on this CPU family. These will be logged in the
+ which is compiled at the start of the tests contains one or more
opcodes
+ which are not implemented on this CPU family. These will be logged in
the
<phrase revision="sysv">system log</phrase>
<phrase revision="systemd">systemd journal</phrase>
and will be followed a few minutes later by segmentation faults.
Despite
@@ -224,7 +223,7 @@
<para>
To run the tests issue
- <command>python3 ./x.py test --verbose --no-fail-fast | tee
rustc-testlog</command>:
+ <command>./x.py test --verbose --no-fail-fast | tee
rustc-testlog</command>:
as with the build, that will use all available CPUs. This runs many
suites
of tests (in an apparently random order), several will fail in BLFS:
compile-fail/issue-37131.rs require a thumbv6m-none-eabi compiler but the
@@ -261,7 +260,7 @@
</para>
<screen><userinput>export LIBSSH2_SYS_USE_PKG_CONFIG=1 &&
-DESTDIR=${PWD}/install python3 ./x.py install &&
+DESTDIR=${PWD}/install ./x.py install &&
unset LIBSSH2_SYS_USE_PKG_CONFIG</userinput></screen>
<para>
Modified: trunk/BOOK/introduction/welcome/changelog.xml
==============================================================================
--- trunk/BOOK/introduction/welcome/changelog.xml Sun Jan 6 15:15:46
2019 (r20926)
+++ trunk/BOOK/introduction/welcome/changelog.xml Sun Jan 6 17:30:32
2019 (r20927)
@@ -45,6 +45,10 @@
<para>January 6th, 2019</para>
<itemizedlist>
<listitem>
+ <para>[ken] - Revert to using python2 for rustc. Fixes
+ <ulink url="&blfs-ticket-root;11520">#11520</ulink>.</para>
+ </listitem>
+ <listitem>
<para>[bdubbs] - Update to thunderbird-60.4.0. Fixes
<ulink url="&blfs-ticket-root;11469">#11469</ulink>.</para>
</listitem>
--
http://lists.linuxfromscratch.org/listinfo/blfs-book
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page