Google Git
Sign in
chromium / external / github.com / llvm / llvm-project / fefa022c8232afddfbca4db0b3366587c9905933
commitfefa022c8232afddfbca4db0b3366587c9905933[log] [tgz]
authorGeorge Burgess IV <[email protected]>Mon Apr 28 18:42:26 2025
committerGeorge Burgess <[email protected]>Tue May 06 20:42:37 2025
tree320f5c62893d1f1fc850ae5343f1ddde032477f1
parente367fc303d6998af2cd2542ca052fa9b122588de [diff]
llvm: don't touch VCS files

Builds of LLVM (& its subpackages) try to touch `.git/logs/HEAD` in
order to be able to cheaply determine when a header file that contains
VCS info should be updated.

As mentioned in the comment, users of this have to gracefully handle the
`touch` failing, but Portage's sandbox reports it as a violation and
fails the build regardless.

Just unconditionally skip touching the file so we avoid the sandbox
issues.

BUG=b:412322904
TEST=`emerge llvm` got to src_compile() instead of dying at
TEST=src_configure().

patch.cherry: false
patch.platforms: chromiumos
patch.version_range.from: 547379
patch.version_range.until: null

Change-Id: I021f090ae609127acb429031277906f9d74c9552
1 file changed
tree: 320f5c62893d1f1fc850ae5343f1ddde032477f1
  1. .ci/
  2. .github/
  3. bolt/
  4. clang/
  5. clang-tools-extra/
  6. cmake/
  7. compiler-rt/
  8. cros/
  9. cross-project-tests/
  10. flang/
  11. libc/
  12. libclc/
  13. libcxx/
  14. libcxxabi/
  15. libunwind/
  16. lld/
  17. lldb/
  18. llvm/
  19. llvm-libgcc/
  20. mlir/
  21. offload/
  22. openmp/
  23. polly/
  24. pstl/
  25. runtimes/
  26. third-party/
  27. utils/
  28. .clang-format
  29. .clang-tidy
  30. .git-blame-ignore-revs
  31. .gitattributes
  32. .gitignore
  33. .mailmap
  34. CODE_OF_CONDUCT.md
  35. CONTRIBUTING.md
  36. LICENSE.TXT
  37. OWNERS
  38. OWNERS.toolchain
  39. PRESUBMIT.cfg
  40. pyproject.toml
  41. README.md
  42. SECURITY.md
README.md

The LLVM Compiler Infrastructure

OpenSSF Scorecard OpenSSF Best Practices libc++

Welcome to the LLVM project!

This repository contains the source code for LLVM, a toolkit for the construction of highly optimized compilers, optimizers, and run-time environments.

The LLVM project has multiple components. The core of the project is itself called “LLVM”. This contains all of the tools, libraries, and header files needed to process intermediate representations and convert them into object files. Tools include an assembler, disassembler, bitcode analyzer, and bitcode optimizer.

C-like languages use the Clang frontend. This component compiles C, C++, Objective-C, and Objective-C++ code into LLVM bitcode -- and from there into object files, using LLVM.

Other components include: the libc++ C++ standard library, the LLD linker, and more.

Getting the Source Code and Building LLVM

Consult the Getting Started with LLVM page for information on building and running LLVM.

For information on how to contribute to the LLVM project, please take a look at the Contributing to LLVM guide.

Getting in touch

Join the LLVM Discourse forums, Discord chat, LLVM Office Hours or Regular sync-ups.

The LLVM project has adopted a code of conduct for participants to all modes of communication within the project.