ccache: upgrade 4.13.6 -> 4.14
PATCH 1/3 ccache: upgrade 4.13.6 -> 4.14
=== Removed functionality
- Removed the cpp_extension (CCACHE_EXTENSION) configuration option since ccache now processes preprocessor output directly in memory instead of using intermediate files. +
=== New features and improvements
- Added support for the QCC (QNX) compiler. +
- Added limited support for caching SARIF diagnostics:
-fdiagnostics-format=sarif-stderr and -fdiagnostics-{add,set}-output=sarif:file=... for GCC, /experimental:log for MSVC.
- Added automatic depend mode for NVCC on Windows.
- Added support for @layout=local in the file storage backend, allowing a copy or read-only mount of a local cache to be used as remote storage.
- Extended the remote storage helper protocol with an exists operation, avoiding transfer of already stored values in reshare mode, and an info operation for reporting the helper's identity and diagnostics.
- Added a --dry-run option for previewing cleanup, eviction and directory trimming operations without removing files.
- Added support for rewriting absolute profile data file paths to relative, improving cache sharing between different directory trees. +
- Added support for reflinking .dwo files when file cloning is enabled. +
- Added detection of C23 #embed directives in direct and depend mode and of assembler .incbin directives in depend mode, preventing false cache hits.
- Added support for -Wp, options with multiple macro definitions.
- Ccache now hashes the contents of Clang module files specified with -fmodule-file=, preventing false cache hits when a module changes.
- Cleanup and eviction operations now print the amount of data and number of files removed.
- Increased the maximum number of raw files stored in a cached result to 256.
- Modernized use of C++ type traits.
- Improved portability of compiler exit status handling.
- Made path rewriting on Windows case-insensitive and Unicode-aware.
- Made ignore_headers_in_manifest match case-insensitively on Windows.
- Reduced the number of system calls for IPC requests.
=== Bug fixes
- Fixed base_dir path rewriting when using MSVC's /Yu option: paths are no longer rewritten to relative when using a precompiled header, since MSVC then does not like relative paths for the /Yu and /FI arguments.
- Fixed handling of compiler options when one recognized option is a prefix of another.
- Fixed base_dir handling for include paths in preprocessor mode (regression in ccache 4.12.2).
- Fixed handling of Clang 22's --warning-suppression-mappings option.
- Fixed error handling when a Clang configuration file cannot be hashed.
- Fixed a remote storage configuration with read_only=false being treated as read-only.
- Fixed interrupted system calls when communicating with remote storage helpers.
- Avoided a race if starting a remote storage helper takes an unexpectedly long time.
- Avoided spawning and waiting for a remote storage helper when IPC access is denied by a sandbox.
- Fixed the free space check for the inode cache.
- Fixed handling of empty atomic file writes and improved robustness if opening an atomic file stream fails.
- Fixed a size overflow when allocating very large files on Windows.
- Fixed thread safety of time conversion fallbacks on systems without gmtime_r and localtime_r.
- Fixed handling of systems that report zero available hardware threads.
- Fixed reporting of errors from posix_spawnp.
- Fixed the statistics counter used when a Clang sanitize ignorelist cannot be read.
=== Build improvements
- Fixed building with Clang 23.
- Added missing CMake probe for gmtime_r.
=== Documentation improvements
- Improved base_dir documentation.
- Clarified syntax of configuration options that take path lists.
---
.../ccache/{ccache_4.13.6.bb => ccache_4.14.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-devtools/ccache/{ccache_4.13.6.bb => ccache_4.14.bb} (93%)meta/recipes-devtools/ccache/ccache_4.14.bb renamed from meta/recipes-devtools/ccache/ccache_4.13.6.bb +1 -1
@@ -16,7 +16,7 @@ DEPENDS = "zstd fmt xxhash" SRC_URI = "${GITHUB_BASE_URI}/download/v${PV}/${BP}.tar.gz" -SRC_URI[sha256sum] = "d42ace95dec14583fb8af19ed117919995bd910376f52d9b6f546046b792dfb7" +SRC_URI[sha256sum] = "fca63f36a83fb2f4b3cc4c01b2c7a1cd6e3629e7f7bd1e01a2eb8810f947c5ab" inherit cmake github-releases
PATCH 2/3 pkgconf: upgrade 3.0.5 -> 3.0.6
Changes from 3.0.5 to 3.0.6:
----------------------------
* Command-line behavior:
- --variable accepts multiple modules and prints the requested variable's value for each module, in argument order. --path and --print-variables remain limited to a single module.
- pccritic no longer reports the PC061 style finding for CRLF line endings, avoiding a noisy warning for normal Windows files.
See https://github.com/pkgconf/pkgconf/issues/587.
* Build and portability fixes:
- Improve OS/2 support by exporting libpkgconf APIs from DLL builds, recognizing OS/2 drive letters and path separators, comparing paths without case sensitivity, and using binary mode for redirected standard output and error. Patches by KO Myung-Hun.
- Declare pkgconf long-path-aware in its Windows application manifest, allowing paths beyond the traditional MAX_PATH limit when long paths are enabled by the operating system. Patch by moi15moi.
---
.../pkgconf/{pkgconf_3.0.5.bb => pkgconf_3.0.6.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-devtools/pkgconf/{pkgconf_3.0.5.bb => pkgconf_3.0.6.bb} (97%)meta/recipes-devtools/pkgconf/pkgconf_3.0.6.bb renamed from meta/recipes-devtools/pkgconf/pkgconf_3.0.5.bb +1 -1
@@ -20,7 +20,7 @@ SRC_URI = "\ file://pkg-config-native.in \ file://pkg-config-esdk.in \ " -SRC_URI[sha256sum] = "3acd3a8a3cce65a8d620321855d92fb602e026cbe8e13ee36bdec58483b59ace" +SRC_URI[sha256sum] = "c88a653fbabfa2a5857a30f6b6ad6c40dbacc3b7c72cc066e5c7dc4571cbddaa" UPSTREAM_CHECK_REGEX = "pkgconf-(?P<pver>\d+\.\d+\.(?!9\d+)\d+)\.tar" inherit autotools pkgconfig
PATCH 3/3 utfcpp: upgrade 4.1.1 -> 4.2.0
In reply to Richard Purdie2d8e20b Release 4.2.0
44fdb26 Update README with project history link
5caca3f Fix exception type in API_REFERENCE.md
87ca49f next16 properly reports errors
c5585ef Reordered validity checks to preserve the earlier behavior.
4f46292 Fixed some warnings in benchmark.cpp
2f74d3b Removed unused is_overlong_sequence()
ef75b56 Rewrote validate_next that returns a code point.
85d5927 Fix bench/compare_commits.py
3145774 Revert the "minor optimization for ASCII range" as it actually hurts performance. ca9e9bc Forgot to include the change for benchmark.cpp
ee0712e Fix the benchmarking script
9fb955a Python script to easily compare performance of two commits.
bf99533 A minor optimization for ASCII range.
---
.../recipes-support/utfcpp/{utfcpp_4.1.1.bb => utfcpp_4.2.0.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-support/utfcpp/{utfcpp_4.1.1.bb => utfcpp_4.2.0.bb} (94%)meta/recipes-support/utfcpp/utfcpp_4.2.0.bb renamed from meta/recipes-support/utfcpp/utfcpp_4.1.1.bb +1 -1
@@ -11,7 +11,7 @@ LIC_FILES_CHKSUM = "file://LICENSE;md5=e4224ccaecb14d942c71d31bef20d78c \ SRC_URI = "git://github.com/nemtrif/utfcpp;protocol=https;branch=master;tag=v${PV} \ file://run-ptest" -SRCREV = "819011bb01628fe1aa2f1da9f2c842a48fd5680b" +SRCREV = "2d8e20b22dcb3e9b3c4f52103182ebda949c6089" inherit cmake ptest
Patchtest results for [PATCH 1/3] ccache: upgrade 4.13.6 -> 4.14
In reply to Richard PurdieThank you for your submission. Patchtest identified one or more issues with the patch. Please see the log below for more information:
---
Testing patch /home/patchtest/share/mboxes/1-3-ccache-upgrade-4.13.6---4.14.patch
FAIL: test commit message user tags: Mbox includes one or more GitHub-style username tags. Ensure that any "@" symbols are stripped out of usernames (test_mbox.TestMbox.test_commit_message_user_tags)
PASS: pretest src uri left files (test_metadata.TestMetadata.pretest_src_uri_left_files)
PASS: test CVE check ignore (test_metadata.TestMetadata.test_cve_check_ignore)
PASS: test Signed-off-by presence (test_mbox.TestMbox.test_signed_off_by_presence)
PASS: test auh changelog truncation notice (test_mbox.TestMbox.test_auh_changelog_truncation_notice)
PASS: test author valid (test_mbox.TestMbox.test_author_valid)
PASS: test commit message presence (test_mbox.TestMbox.test_commit_message_presence)
PASS: test lic files chksum modified not mentioned (test_metadata.TestMetadata.test_lic_files_chksum_modified_not_mentioned)
PASS: test max line length (test_metadata.TestMetadata.test_max_line_length)
PASS: test mbox format (test_mbox.TestMbox.test_mbox_format)
PASS: test non-AUH upgrade (test_mbox.TestMbox.test_non_auh_upgrade)
PASS: test shortlog format (test_mbox.TestMbox.test_shortlog_format)
PASS: test shortlog length (test_mbox.TestMbox.test_shortlog_length)
PASS: test src uri left files (test_metadata.TestMetadata.test_src_uri_left_files)
PASS: test target mailing list (test_mbox.TestMbox.test_target_mailing_list)
SKIP: pretest pylint: No python related patches, skipping test (test_python_pylint.PyLint.pretest_pylint)
SKIP: test CVE tag format: No new source patches introduced (test_patch.TestPatch.test_cve_tag_format)
SKIP: test Signed-off-by presence: No new source patches introduced (test_patch.TestPatch.test_signed_off_by_presence)
SKIP: test Upstream-Status presence: No new source patches introduced (test_patch.TestPatch.test_upstream_status_presence_format)
SKIP: test bugzilla entry format: No bug ID found (test_mbox.TestMbox.test_bugzilla_entry_format)
SKIP: test lic files chksum presence: No added recipes, skipping test (test_metadata.TestMetadata.test_lic_files_chksum_presence)
SKIP: test license presence: No added recipes, skipping test (test_metadata.TestMetadata.test_license_presence)
SKIP: test pylint: No python related patches, skipping test (test_python_pylint.PyLint.test_pylint)
SKIP: test series merge on head: Merge test is disabled for now (test_mbox.TestMbox.test_series_merge_on_head)
SKIP: test summary presence: No added recipes, skipping test (test_metadata.TestMetadata.test_summary_presence)
---
Please address the issues identified and
submit a new revision of the patch, or alternatively, reply to this email with an explanation of why the patch should be accepted. If you believe these results are due to an error in patchtest, please submit a bug at https://bugzilla.yoctoproject.org/ (use the 'Patchtest' category under 'Yocto Project Subprojects'). For more information on specific failures, see: https://wiki.yoctoproject.org/wiki/Patchtest. Thank you!