Changeset 326f830 for general/prog
- Timestamp:
- 01/24/2018 01:54:48 AM (6 years ago)
- Branches:
- 10.0, 10.1, 11.0, 11.1, 11.2, 11.3, 12.0, 12.1, 8.2, 8.3, 8.4, 9.0, 9.1, basic, bdubbs/svn, elogind, kea, ken/TL2024, ken/inkscape-core-mods, ken/tuningfonts, lazarus, lxqt, perl-modules, 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:
- 13df334
- Parents:
- a37cebb
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
general/prog/rust.xml
ra37cebb r326f830 7 7 <!ENTITY rust-download-http "https://static.rust-lang.org/dist/rustc-&rust-version;-src.tar.gz"> 8 8 <!ENTITY rust-download-ftp " "> 9 <!ENTITY rust-md5sum "7 5e779670ac79edf023497a9c37eb35d">10 <!ENTITY rust-size " 48MB">11 <!ENTITY rust-buildsize "4. 2 GB (362 MB installed), (add 0.6GB for tests) plus 273MB for ~/.cargo files">12 <!ENTITY rust-time " 33 SBU (add 14 SBU for tests, both with 4 processors)">9 <!ENTITY rust-md5sum "7272ddba14f512e6d2612ef60460bed8"> 10 <!ENTITY rust-size "53 MB"> 11 <!ENTITY rust-buildsize "4.1 GB (437 MB installed), (add 1.2GB for tests) including 226MB of ~/.cargo files for both the builder and root (from the install)"> 12 <!ENTITY rust-time "48 SBU (add 12 SBU for tests, both with 4 processors)"> 13 13 ]> 14 14 … … 54 54 </para> 55 55 56 <note> 57 <para> 58 Repeated builds of this package on the same machine show a wide range 59 of build times. Some of this might be due to variations in downloading 60 the required cargo files if they are not already present, but this does 61 not seem to adequately explain the variations. Also, both the builder 62 and the user running the install will need to download the cargo crates 63 if they are not already present in <filename>~/.cargo</filename>. 64 </para> 65 <para> 66 If you use a DESTDIR method to install, you will only need to download 67 the crates once, for the build, saving about one-third of the build and 68 install time (but using extra space for the install). Similarly if you 69 were to build as root, or if your user is allowed to run <command>sudo 70 ./x.py install</command> - but those methods are dangerous. 71 </para> 72 </note> 73 56 74 &lfs81_checked; 57 75 … … 96 114 <xref linkend="curl"/>, 97 115 <xref linkend="cmake"/>, 116 <!-- if changing this to use python3, also add python2 as a required 117 dependency for firefox, because at the moment it picks that up from here --> 98 118 <xref linkend="python2"/> 99 119 </para> … … 127 147 128 148 <screen><userinput>cat <<EOF > config.toml 129 # see src/bootstrap/config.toml.example for more possible options149 # see config.toml.example for more possible options 130 150 [llvm] 131 151 targets = "X86" … … 137 157 [install] 138 158 prefix = "/usr" 139 docdir = "share/doc/rustc-1.19.0" 159 docdir = "share/doc/rustc-&rust-version;" 160 161 [rust] 140 162 channel = "stable" 163 rpath = false 141 164 EOF</userinput></screen> 142 165 … … 156 179 compile for the thumbv6m-none-eabi target, but the BLFS build does not cater for 157 180 that, and all 105 tests in debuginfo-gdb will fail if 158 <application>gdb</application> has not been installed. 181 <application>gdb</application> has not been installed. Several other tests in 182 run-make can also fail. 159 183 </para> 160 184 … … 167 191 168 192 <para> 169 That should report 14 029tests. Similarly, the total tests which failed can193 That should report 14854 tests. Similarly, the total tests which failed can 170 194 be found by running: 171 195 </para> … … 205 229 206 230 <para> 231 <command>rpath = false</command>: by default, <command>rust</command> can 232 be run from where it was built, without being installed. That adds DT_RPATH 233 entries to all of the ELF files, which produces very messy output from 234 <command>ldd</command>, showing the libraries in the place they were built, 235 even if they have been deleted from there after the install. 236 </para> 237 238 <para> 207 239 <command>--verbose</command>: this switch can sometimes provide more 208 240 information about a test which fails. … … 212 244 <command>--no-fail-fast</command>: this switch ensures that the testsuite 213 245 will not stop at the first error. 246 </para> 247 248 <para> 249 <option>PYTHON=/usr/bin/python3 ... tee buildlog</option>: Because rust 250 can use <application>Python3</application> which was installed in LFS, 251 this command tells it to use that instead of the deprecated 252 <application>Python2</application>. For the moment this should be regarded 253 as experimental and problems may be encountered. Because 254 <application>rust</application> will use all CPUs, if an error happened the 255 message may have scrolled out of the terminal's buffer. Logging makes it 256 possible to find out what was reported. 214 257 </para> 215 258 … … 226 269 <seglistitem> 227 270 <seg> 228 cargo, r ust-gdb, rust-lldb, rustc, rustdoc.271 cargo, rls, rust-gdb, rust-lldb, rustc, rustdoc. 229 272 </seg> 230 273 <seg> … … 257 300 </varlistentry> 258 301 302 <varlistentry id="rls"> 303 <term><command>rls</command></term> 304 <listitem> 305 <para> 306 is the Rust Language Server. This can run in the background to 307 provide IDEs, editors, and other tools with information about Rust 308 programs. 309 </para> 310 <indexterm zone="rust rls"> 311 <primary sortas="b-rls">rls</primary> 312 </indexterm> 313 </listitem> 314 </varlistentry> 315 259 316 <varlistentry id="rust-gdb"> 260 317 <term><command>rust-gdb</command></term>
Note:
See TracChangeset
for help on using the changeset viewer.