- Timestamp:
- 01/27/2019 02:38:43 AM (5 years ago)
- Branches:
- 10.0, 10.1, 11.0, 11.1, 11.2, 11.3, 12.0, 12.1, 8.4, 9.0, 9.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:
- 4f8ca94
- Parents:
- 4cc77fbd
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
general/prog/rust.xml
r4cc77fbd rd396c65 74 74 <note> 75 75 <para> 76 When you upgrade to a newer version, the new libraries will have various 77 hashes in their names and therefore there will be a mix of versions but 78 only one of each will be usable. A binary distribution would use its 79 package manager to delete all the old <application>rust</application> 80 installation before updating. You may wish to do the same to save space. 81 </para> 82 83 <para> 84 One alternative when working with multiple versions or just updating 85 to a new version is to place the files in the 86 <filename class="directory">/opt</filename> directory. The instructions 87 below provide optional commands to support better control of 88 new package versions or reinstallation of the current version. 76 Although BLFS usually installs in <filename 77 class="directory">/usr</filename>, when you later upgrade to a newer 78 version of <application>rust</application> the old libraries in <filename 79 class="directory">/usr/lib/rustlib</filename> will remain, with various 80 hashes in their names, but will not be usable and will waste space. The 81 editors recommend placing the files in the <filename 82 class="directory">/opt</filename> directory. In particular, if you 83 have reason to rebuild with a modified configuration (e.g. using the 84 shipped LLVM after building with shared LLVM, but perhaps also the 85 reverse situation) it it possible for the install to leave a broken 86 <command>cargo</command> program. In such a situation, either remove 87 the existing installation first, or use a different prefix such as 88 /opt/rustc-&rust-version;-build2. 89 </para> 90 91 <para> 92 If you prefer, you can of course change the prefix to <filename 93 class="directory">/usr</filename> and omit the 94 <command>ldconfig</command> and the actions to add rustc to the PATH. 89 95 </para> 90 96 </note> … … 105 111 Rustc defaults to building for ALL supported architectures, using a 106 112 shipped copy of LLVM. In BLFS the build is only for the X86 architecture. 107 If you intend to develop rust crates, this build may not be good 113 If you intend to develop rust crates, this build may not be good 108 114 enough for your purposes. 109 115 </para> … … 188 194 189 195 <para> 190 If you are going to install into the 191 <filename class="directory">/opt</filename> directory, remove 192 conflicting entries and recreate the required entries. 196 To install into the 197 <filename class="directory">/opt</filename> directory, remove the symlink 198 and create a new directory (i.e. with a different name if trying a 199 modified build). 193 200 As the <systemitem class="username">root</systemitem> 194 201 user: 195 202 </para> 196 203 197 <screen role="root"><userinput>rm -rf /opt/rustc /opt/rustc-&rust-version; && 198 mkdir /opt/rustc-&rust-version; && 199 ln -sv rustc-&rust-version; /opt/rustc</userinput></screen> 204 <screen role="root"><userinput>mkdir /opt/rustc-&rust-version; && 205 ln -svfin rustc-&rust-version; /opt/rustc</userinput></screen> 200 206 201 207 <note> … … 338 344 <sect2 role="commands"> 339 345 <title>Command Explanations</title> 346 347 <para> 348 <command>ln -svfn rustc-&rust-version; /opt/rustc</command>: if this is 349 not the first use of the <filename class="directory">/opt/rustc</filename> 350 symlink, overwrite it by forcing, and use the '-n' flag to avoid getting 351 confusing results from e.g. <command>ls -l</command>. 352 </para> 340 353 341 354 <para>
Note:
See TracChangeset
for help on using the changeset viewer.