Beyond Linux From Scratch/general_prog_llvm — English @ LFS Translation Server: If <option>-jN</option> (N replaced with a number) is passed to …

Source string Source string

English

If <option>-jN</option> (N replaced with a number) is passed to <command>ninja</command>, the tests will be built with N logical cores, but run using all available logical cores.  Run the test command in a cgroup (<phrase revision='systemd'>pass the <option>-p AllowedCPUs=...</option> option to the <command>systemd-run</command> command, </phrase> read <xref linkend='build-in-cgroup'/> for details) to limit the number of logical cores for running the tests.  One test named <filename>Linux/clone_setns.cpp</filename> will fail if <option>CONFIG_USER_NS</option> is not enabled in kernel configuration.

Needs editing

The string is read only.

Skip

	English	Actions
	If you have downloaded <application>compiler-rt</application>, install it into the source tree by running the following commands:
	<userinput>tar -xf ../compiler-rt-&llvm-version;.src.tar.xz -C projects && mv projects/compiler-rt-&llvm-version;.src projects/compiler-rt</userinput>
	There are many Python scripts in this package which use <command>/usr/bin/env python</command> to access the system Python which on LFS is <xref linkend="python3"/>. Use the following command to fix these scripts:
	<userinput>grep -rl '#!.*python' \| xargs sed -i '1s/python$/python3/'</userinput>
	Install <application>LLVM</application> by running the following commands:
	<userinput>mkdir -v build && cd build && CC=gcc CXX=g++ \ cmake -DCMAKE_INSTALL_PREFIX=/usr \ -DLLVM_ENABLE_FFI=ON \ -DCMAKE_BUILD_TYPE=Release \ -DLLVM_BUILD_LLVM_DYLIB=ON \ -DLLVM_LINK_LLVM_DYLIB=ON \ -DLLVM_ENABLE_RTTI=ON \ -DLLVM_TARGETS_TO_BUILD="host;AMDGPU" \ -DLLVM_BINUTILS_INCDIR=/usr/include \ -DLLVM_INCLUDE_BENCHMARKS=OFF \ -DCLANG_DEFAULT_PIE_ON_LINUX=ON \ -DCLANG_CONFIG_FILE_SYSTEM_DIR=/etc/clang \ -Wno-dev -G Ninja .. && ninja</userinput>
	If you have installed <xref linkend="recommonmark"/> and its dependencies, you can generate the html documentation and manual pages with the following commands:
	<userinput>cmake -DLLVM_BUILD_DOCS=ON \ -DLLVM_ENABLE_SPHINX=ON \ -DSPHINX_WARNINGS_AS_ERRORS=OFF \ -Wno-dev -G Ninja .. && ninja docs-llvm-html docs-llvm-man</userinput>
	The clang documentation can be built too:
	<userinput>ninja docs-clang-html docs-clang-man</userinput>
	If you wish to run the tests, remove a test case known to hang indefinitely on some systems:
	<userinput>rm -f ../projects/compiler-rt/test/tsan/getline_nohang.cpp</userinput>
	LLVM test suite can produce many core dump files. They will occupy a large amount of disk space, and the core dump process can significantly slow down the testing. To test the results with core dump disabled, <phrase revision='systemd'>ensure <xref linkend='systemd'/> and <xref linkend='shadow'/> have been rebuilt with <xref linkend='linux-pam'/> support (if you are interacting via a SSH or graphical session, also ensure the <xref linkend='openssh'/> server or the desktop manager has been built with <xref linkend='linux-pam'/>) and the current login session is started after updating the <filename>/etc/pam.d/system-session</filename> file to include <filename class='libraryfile'>pam_systemd.so</filename>, then </phrase>issue:
	<userinput>sh -c 'ulimit -c 0 && ninja check-all'</userinput>
	<userinput>systemctl --user start dbus && systemd-run --user --pty -d -G -p LimitCORE=0 ninja check-all</userinput>
	If <option>-jN</option> (N replaced with a number) is passed to <command>ninja</command>, the tests will be built with N logical cores, but run using all available logical cores. Run the test command in a cgroup (<phrase revision='systemd'>pass the <option>-p AllowedCPUs=...</option> option to the <command>systemd-run</command> command, </phrase> read <xref linkend='build-in-cgroup'/> for details) to limit the number of logical cores for running the tests. One test named <filename>Linux/clone_setns.cpp</filename> will fail if <option>CONFIG_USER_NS</option> is not enabled in kernel configuration.
	Now, as the &root; user:
	<userinput>ninja install && cp bin/FileCheck /usr/bin</userinput>
	If you have built the llvm documentation, it has been installed by the above command, but it needs to be moved. As the <systemitem class="username">root</systemitem> user:
	<userinput>install -v -d -m755 /usr/share/doc/llvm-&llvm-version; && mv -v /usr/share/doc/LLVM/llvm /usr/share/doc/llvm-&llvm-version; && rmdir -v --ignore-fail-on-non-empty /usr/share/doc/LLVM</userinput>
	If you have built the clang documentation, it has been installed, but needs to be moved too. Again as the <systemitem class="username">root</systemitem> user:
	<userinput>install -v -d -m755 /usr/share/doc/llvm-&llvm-version; && mv -v /usr/share/doc/LLVM/clang /usr/share/doc/llvm-&llvm-version; && rmdir -v --ignore-fail-on-non-empty /usr/share/doc/LLVM</userinput>
	Command Explanations
	<parameter>-DLLVM_ENABLE_FFI=ON</parameter>: This switch allows <application>LLVM</application> to use <application>libffi</application>.
	<parameter>-DLLVM_BUILD_LLVM_DYLIB=ON</parameter>: This switch builds the libraries as static and links all of them into an unique shared one. This is the recommended way of building a shared library.
	<parameter>-DCMAKE_BUILD_TYPE=Release</parameter>: This switch enables compiler optimizations in order to speed up the code and reduce its size. It also disables some compile checks which are not necessary on a production system.
	<parameter>-DLLVM_TARGETS_TO_BUILD="host;AMDGPU"</parameter>: This switch enables building for the same target as the host, and also for the r600 AMD GPU used by the Mesa r600 and radeonsi drivers. The default is all of the targets. You can use a semicolon separated list. Valid targets are: host, AArch64, AMDGPU, ARM, AVR, BPF, Hexagon, Lanai, LoongArch, Mips, MSP430, NVPTX, PowerPC, RISCV, Sparc, SystemZ, SystemZ, VE, WebAssembly, X86, XCore, or all.
	<parameter>-DLLVM_LINK_LLVM_DYLIB=ON</parameter>: Used in conjunction with <parameter>-DLLVM_BUILD_LLVM_DYLIB=ON</parameter>, this switch enables linking the tools against the shared library instead of the static ones. It slightly reduces their size and also ensures that llvm-config will correctly use libLLVM-&llvm-maj-version;.so.
	<parameter>-DLLVM_ENABLE_RTTI=ON</parameter>: This switch is used to build LLVM with run-time type information. This is required for building <xref linkend="mesa"/>.
	<parameter>-DLLVM_BINUTILS_INCDIR=/usr/include</parameter>: This switch is used to tell the build system the location of binutils headers, which were installed in LFS. This allows the building of <filename class="libraryfile">LLVMgold.so</filename>, which is needed for building programs with <command>clang</command> and Link Time Optimization (LTO).
	<parameter>-DLLVM_INCLUDE_BENCHMARKS=OFF</parameter>: is used to disable generation build targets for the LLVM benchmarks. This option requires additional code that is not currently available.

Loading…

None

Source string added

If <option>-jN</option> (N replaced with a number) is passed to <command>ninja</command>, the tests will be built with N logical cores, but run using all available logical cores. Run the test command in a cgroup (<phrase revision='systemd'>pass the <option>-p AllowedCPUs=...</option> option to the <command>systemd-run</command> command, </phrase> read <xref linkend='build-in-cgroup'/> for details) to limit the number of logical cores for running the tests. One test named <filename>Linux/clone_setns.cpp</filename> will fail if <option>CONFIG_USER_NS</option> is not enabled in kernel configuration.

a month ago

Browse all string changes

Things to check

Ellipsis

The string uses three dots (...) instead of an ellipsis character (…)

Reset

Glossary

English	English
No related strings found in the glossary.

String information

Source string description

EDITORS - if you have more than 4 cores, use a cgroup to measure the elapsed time for the tests. Also, libstdc++.a and perhaps libstdc++fs.a are used by a couple of the link-static tests. 18.1.2: 71626 Passed, 27447 Unsupported, 339 Skipped, 133 Expectedly Failed To editors: it seems there is a more thorough test suite named "test-suite-x.y.z.src.tar.xz" on the GitHub release download page. The usage of it is on https://llvm.org/docs/TestSuiteGuide.html. It looks like we've never mentioned it in BLFS. Let's let it go. llvm is complex enough as it is. Adding the additional testsuite is IMO overkill. - bdubbs type: Content of: <sect1><sect2><para>

Flags

read-only, xml-text

Source string location

blfs-en/general/prog/llvm.xml:361

String age

a month ago

Last updated

a month ago

Source string age

a month ago

Translation file

string 76