Repository navigation
Fail the macOS build when the D runtime lookup fails - #2
Conversation
Signed-off-by: Anish Pallati <i@anish.land>
|
Navigate logical layers of code changes, visualize relationships, and explore their blast radius. No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (1)
Included review availability: This review used your included allowance. Your plan provides up to 10 included reviews per hour; 9 remain after this review. 📝 WalkthroughWalkthroughThe macOS build script now resolves runtime libraries before calling ChangesRuntime library build
Priority: ⬇️ Low Estimated code review effort: 2 (Simple) | ~5 minutes Change: Bug fix Merge Risk: ⚪ Minimal · up to The runtime lookup now occurs before archive creation, and callers do not suppress failure handling. Architecture SummaryArchitecture risk: 🔵 Low · up to The change affects 1 system. Changed systems: Architecture concerns Review detailsSystems and components
Before / after behavior
🚥 Pre-merge checks | ✅ 4✅ Passed checks (4 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
If
find_runtime_librariescan't find phobos/druntime it prints an error and exits 1, but since it's called inside$(...)as an argument to libtool,set -edoesn't catch it.Instead, the build keeps going and you end up with a
libxadibase.athat doesn't have the D runtime in it, which only shows up later as undefined symbol errors when linking. We can assign it to a variable first to make the build stop there instead.I ran into this packaging xadi for nixpkgs, where the lookup failed and the build still succeeded.
Summary by CodeRabbit