mirror of
https://github.com/mozilla/gecko-dev.git
synced 2024-11-29 07:42:04 +00:00
9f6417f045
I was able to reproduce the failure to apply llvm-dsymutil on the last mozilla-central revision before debug info was temporarily disabled for rust, and validated that the problem was gone in clang 4. After some bisection, r289565 was identified as having fixed the problem, which, reading the commit message, makes sense. It was however not possible to simply cherry-pick, because of multiple code changes between 3.9 and 4. However, apart from the volume of conflicting changes, it was more or less straightforward to backport. Interestingly, the patch for r313872 was relying on changes from r289565, which is why it required a variant specifically for 3.9, but now we can use the same patch as for other versions. Well, except there's a small difference in the context, and build-clang.py doesn't allow fuzz, so we manually edit the patch to remove that line from the context. --HG-- extra : rebase_source : de0ab262d401c37c0e9300b0ef7923a07c009d87 |
||
---|---|---|
.. | ||
build-clang.py | ||
clang-3.9-linux64.json | ||
clang-4-linux64.json | ||
clang-5-linux64.json | ||
clang-6-pre-linux64.json | ||
clang-macosx64.json | ||
clang-tidy-linux64.json | ||
clang-tidy-macosx64.json | ||
clang-tidy-win32.json | ||
clang-tidy-win64.json | ||
clang-win32.json | ||
clang-win64.json | ||
compiler-rt-cross-compile.patch | ||
fflush-before-unlocking.patch | ||
find_symbolizer_linux.patch | ||
hide-gcda-profiling-symbols.patch | ||
llvm-debug-frame-for-5.patch | ||
llvm-debug-frame.patch | ||
loosen-msvc-detection.patch | ||
msvc-host-x64.patch | ||
pr28831-r280042.patch | ||
pr_set_ptracer.patch | ||
r277806.patch | ||
r285657.patch | ||
r289565-for-3.9.patch | ||
r313872.patch | ||
r318309.patch | ||
README | ||
return-empty-string-non-mangled.patch |
build-clang.py ============== A script to build clang from source. ``` usage: build-clang.py [-h] -c CONFIG [--clean] optional arguments: -h, --help show this help message and exit -c CONFIG, --config CONFIG Clang configuration file --clean Clean the build directory ``` Pre-requisites -------------- * Working build toolchain. * Subversion * CMake * Ninja * Python 2.7 Please use the latest available CMake for your platform to avoid surprises. Config file format ------------------ build-clang.py accepts a JSON config format with the following fields: * llvm_revision: The LLVM SVN revision to build. * stages: Use 1, 2, or 3 to select different compiler stages. The default is 3. * llvm_repo: SVN path to the LLVM repo. * clang_repo: SVN path to the Clang repo. * extra_repo: SVN path to the clang-tools-extra repo. * lld_repo: SVN path to the lld repo. * compiler_repo: SVN path to the compiler-rt repo. * libcxx_repo: SVN path to the libcxx repo. * libcxxabi_repo: SVN path to the libcxxabi repo. * python_path: Path to the Python 2.7 installation on the machine building clang. * gcc_dir: Path to the gcc toolchain installation, only required on Linux. * cc: Path to the bootsraping C Compiler. * cxx: Path to the bootsraping C++ Compiler. * as: Path to the assembler tool. * ar: Path to the library archiver tool. * ranlib: Path to the ranlib tool (optional). * libtool: Path to the libtool tool (optional). * ld: Path to the linker. * patches: Optional list of patches to apply. * build_type: The type of build to make. Supported types: Release, Debug, RelWithDebInfo or MinSizeRel. * build_libcxx: Whether to build with libcxx. The default is false. * build_clang_tidy: Whether to build clang-tidy with the Mozilla checks imported. The default is false. * osx_cross_compile: Whether to invoke CMake for OS X cross compile builds. * assertions: Whether to enable LLVM assertions. The default is false. Environment Variables --------------------- The following environment variables are used for cross-compile builds targeting OS X on Linux. * CROSS_CCTOOLS_PATH: Path to the cctools directory where the cross compiler toolchain is located. * CROSS_SYSROOT: Path to the OS X SDK directory for cross compile builds.