The version of the libc library built by crosstool-ng is 2.12.2 The version of the GCC compiler built by crosstool-ng is 8.3.0 The version of crosstool-ng used is 1.24.0 Use the stage1 Clang, libunwind, libc++/c++abi, compiler-rt builtins, to build a final/full toolchain.Use the stage1 Clang to compile a stage1 libunwind (static only).Use the stage1 Clang/lld to compile the rest of compiler-rt (*san libraries) and link them to the stage1 compiler-rt builtins.Use the stage1 Clang/lld to compile a stage1 libc++, which will use the previously compiled compiler-rt.Use the stage1 Clang to compile a stage1 compiler-rt (builtins only).Compile a first Clang and lld (stage1), which uses libstdc++.Link all GCC binaries into the sysroot created by crosstool-ng, so that the sysroot can be used for the next steps.Compile an older libz/zlib which is compatible with the old glibc.Use crosstool-ng to compile a stage0 GCC static toolchain, which might be newer than the one available in the system.The rough steps used to achieve the above goals: Typically libc, libdl, librt, libpthread. To do so, the output binary should depend only on shared libraries which are deeply connected with the environment they run on,
OSQUERY OTHER LIBRARY PORTABLE
The toolchain should be able to produce binaries that are portable and run on libc >= 2.12.The toolchain lives in a sysroot folder which should be self sufficient.The toolchain is compiled with a specific glibc version, so that it runs on a wide range of distributions.Obtain a LLVM/Clang toolchain which is portable and which doesn't depend from libstdc++ or libgcc.The procedure to build such a toolchain has been based on the build-anywhere project: įollowing the main goals of the toolchain: The script in this repository is used to build the LLVM/Clang toolchain which is used in the osquery project to create portable binaries of it.
0 kommentar(er)
