chore(server): vcpkg 2026.04.27#1020
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (3)
📝 WalkthroughWalkthroughThis PR contains three independent maintenance updates: extending the CI workflow's change detection to treat ChangesMaintenance and Build Configuration Updates
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Possibly related PRs
Suggested labels
Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
No description provided. |
…survives ROOT CAUSE of the repo-wide Ubuntu Build failure (since GHA ubuntu-22.04 image 20260525, 2026-05-25): detect_installed_clang() returned the HIGHEST versioned clang (15), but the image's default toolchain is clang-14 with the UNVERSIONED libc++-dev/libc++abi-dev owning the multiarch symlink /usr/lib/x86_64-linux-gnu/libc++.so. compiler-unix.sh then force-installed libc++-15-dev; apt resolved the conflict by REMOVING libc++-dev + libc++abi-dev (8 pkgs total), deleting that symlink. Every subsequent '-stdlib=libc++' link failed with 'ld: cannot find -lc++', which CMake surfaced as the misleading 'CMAKE_MAKE_PROGRAM/CMAKE_CXX_COMPILER not set, Ninja not found' cascade in vcpkg detect_compiler. Ninja, cmake, and the vcpkg version were all red herrings (confirmed: PR #1020's 2026.04.27 bump fails Ubuntu identically; the real err.log shows the libc++ link error). Fix: prefer the distro-DEFAULT unversioned clang in detect_installed_clang, falling back to the highest versioned clang only when no default exists. This keeps the compiler aligned with its already-installed, multiarch-symlinked libc++ — no apt removal, -lc++ resolves, build links. Also reverts the clang-15 _build.yaml env pins + diagnostic step (they addressed the wrong layer). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
…Ubuntu CI (#1022) * fix(autoinstall): align clang to distro default so libc++ -lc++ link survives Repo-wide Ubuntu Build failure since GHA ubuntu-22.04 image 20260525 (2026-05-25): the image made default clang=14 while also shipping clang-15. detect_installed_clang() picked the highest (15), so the libc++ check force-installed libc++-15-dev; apt resolved the conflict by REMOVING the unversioned libc++-dev/libc++abi-dev that own the multiarch /usr/lib/x86_64-linux-gnu/libc++.so symlink. Every '-stdlib=libc++' link then failed with 'ld: cannot find -lc++', which CMake surfaced as the misleading vcpkg detect_compiler 'CMAKE_MAKE_PROGRAM/CMAKE_CXX_COMPILER not set, Ninja not found' cascade. (vcpkg/cmake/ninja versions were all red herrings — confirmed: bumping vcpkg to 2026.04.27 in #1020 fails Ubuntu identically.) Fix: prefer the distro-DEFAULT unversioned clang in detect_installed_clang, falling back to the highest versioned clang only when no default exists. Keeps the compiler aligned with its already-installed, multiarch-symlinked libc++ — no apt removal, -lc++ resolves. Verified all-green (Ubuntu + Windows + macOS) on the dot-release branch. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * fix(autoinstall): fall back to bare clang when versioned frontend is absent select_linux_triplet pinned CC/CXX to clang-${CLANG_VERSION} for the already-installed-clang path, but detect_installed_clang only proves the bare `clang` exists — not the versioned clang-N/clang++-N frontend. On setups where clang is provided via update-alternatives or a source build without versioned symlinks, that set an invalid CC/CXX that only failed later at compile time. Guard the versioned frontend and fall back to bare clang/clang++ (which is the detected default, so libc++ stays consistent). Addresses CodeRabbit review on #1022. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com> Co-authored-by: Dmitrii Kataraev <dmitrii.kataraev@rocketride.ai>
vcpkg 2026.04.27's aws-sdk-cpp adds `typedef E ERROR;` in Outcome.h, which collides with the GDI `ERROR` macro pulled in via `atlbase.h`. Push/undef/pop `ERROR` around the AWS includes in `engLib/headers.h`.
d16eab8 to
7809d8a
Compare
VCPKG upgraded to 2026.04.27
Summary by CodeRabbit
Chores
Bug Fixes