Documentation says the threshold is 150MB, but the actual value was 200MB. Fixing this with a correct value, documentation (and previous commit message) are right here.
Thanks to vkadlcik@redhat.com for spotting the issue.
The library size can vary a bit, 100MB is sort of correct, but e.g. RHSCL version is 106MB. Bumping the size threshold to 150MB, it should b still safely within the original bug report of 2GB.
By reverting this we fix these errors:
CMake Error at /usr/lib64/cmake/llvm/AddLLVM.cmake:1821 (add_dependencies):
The dependency target "LLVMHello" of target "check-all" does not exist.
Call Stack (most recent call first):
CMakeLists.txt:578 (add_lit_target)
CMake Error at /usr/lib64/cmake/llvm/AddLLVM.cmake:1821 (add_dependencies):
The dependency target "LLVMHello" of target "check-clang-tools" does not
exist.
Call Stack (most recent call first):
/usr/lib64/cmake/llvm/AddLLVM.cmake:1842 (add_lit_target)
/builddir/build/BUILD/clang-tools-extra-15.0.0.src/test/CMakeLists.txt:110 (add_lit_testsuite)
CMake Error at /usr/lib64/cmake/llvm/AddLLVM.cmake:1821 (add_dependencies):
The dependency target "LLVMHello" of target "check-clang-extra-unit" does
not exist.
Call Stack (most recent call first):
/usr/lib64/cmake/llvm/AddLLVM.cmake:1877 (add_lit_target)
/builddir/build/BUILD/clang-tools-extra-15.0.0.src/test/CMakeLists.txt:118 (add_lit_testsuites)
* upstream/rawhide:
tests: CRB in CentOS has different name
Update to LLVM 13.0.1 final
Switch to an unconditionally applied patch
Revert "Set _package_note_linker on arm"
Disable CrashRecoveryTest.DumpStackCleanup test on aarch64
Fix rpm build warning/error: absolute symlink
Set _package_note_linker on arm
Update to LLVM 13.0.1rc3
- Rebuilt for https://fedoraproject.org/wiki/Fedora_36_Mass_Rebuild
Remove no longer necessary patch
Update to LLVM 13.0.1rc2
lld and libomp are not shipped in s390x, hence causing provisioning
prepare step to fail as they are required in llvm-integration-testsuite.
The test should still run fine without those packages.
I noticed that warnings and errors show up in the `RPM build errors:`
output. When I produced an error I did see this warning about absolute
symlink showing up:
```
absolute symlink: /usr/lib64/bfd-plugins/LLVMgold.so -> /usr/lib64/LLVMgold.so
```
The upstream RPM fix to log warnings and errors separately is here:
https://github.com/rpm-software-management/rpm/pull/1590
Thanks to @sergesanspaille for the help.
On ARM, the default linker is lld when using the clange toolchain,
so specify that as the _package_note_linker. This will use the
-T rather than -dT option for the package note script.
Ideally this would be handled in a more central location.
Increase verbosity for %autosetup
Modified patch so it cleanly applies
Renaming man pages is no longer needed
Fix this error:
mv /builddir/build/BUILDROOT/llvm-13.0.0~pre20210427.gd122d80b3d1c3f-1.fc35.x86_64/usr/share/man/man1/clang-tblgen.1 /builddir/build/BUILDROOT/llvm-13.0.0~pre20210427.gd122d80b3d1c3f-1.fc35.x86_64/usr/share/man/man1/lldb-tblgen.1 /builddir/build/BUILDROOT/llvm-13.0.0~pre20210427.gd122d80b3d1c3f-1.fc35.x86_64/usr/share/man/man1/llvm-tblgen.1 /builddir/build/BUILDROOT/llvm-13.0.0~pre20210427.gd122d80b3d1c3f-1.fc35.x86_64/usr/share/man/man1/mlir-tblgen.1 /builddir/build/BUILDROOT/llvm-13.0.0~pre20210427.gd122d80b3d1c3f-1.fc35.x86_64/usr/share/man/man1/tblgen.1 /builddir/build/BUILDROOT/llvm-13.0.0~pre20210427.gd122d80b3d1c3f-1.fc35.x86_64/usr/share/man/man1/llvm-tblgen.1
mv: target '/builddir/build/BUILDROOT/llvm-13.0.0~pre20210427.gd122d80b3d1c3f-1.fc35.x86_64/usr/share/man/man1/llvm-tblgen.1' is not a directory
Add entry for changelog when building a snapshot
Reset 0001-PATCH-llvm-Make-source-interleave-prefix-test-case-c.patch because it is not applicable to LLVM 12
Moved BuildRequires: python3-psutil out in PR
See https://src.fedoraproject.org/rpms/llvm/pull-request/91
Make download path for snapshot sources-easily adjustable
Added cmake subpackage with shared cmake files
Install cmake files into /usr/lib64/cmake/llvm with the llvm-devel pkg
My expectation is that in the future, more tests will land in this git,
and not all of them would be useful in gating time. AFAIK, CI systems do
run everything they can, therefore adding `when` to control when the
plan is executed - `is not defined` bit should allow anyone to run it
manually, while the rest of the condition should limit its presence to
gating events.
