Bug #62097
closed
Quincy and pacific fail to compile after Boost upgrade of main
Added by Adam Emerson 10 months ago.
Updated 10 months ago.
Description
After upgrading Boost on main, the Jenkins `make check` job fails on both quincy and pacific. This is caused by two issues:
1. install-deps on Quincy and Pacific was never updated after the switch to Jammy and it wouldn't surprise me if it'd been building against the wrong packages for a while now.
2. Boost.Phoenix 1.81 introduces an ODR-violation. A workaround for it is included in main, but not in anything earlier. It's probably worth including anyway in case someone tries to compile on a newer boost.
- Subject changed from quincy and pacific build against older Boost package, fail to compile to Quincy and pacific fail to compile after Boost upgrade of main
- Status changed from In Progress to Fix Under Review
- Pull request ID set to 52559
- Severity changed from 3 - minor to 2 - major
- Copied to Backport #62101: reef: Quincy and pacific fail to compile after Boost upgrade of main added
- Target version deleted (
v17.2.7)
- Backport changed from pacific to reef,quincy,pacific
- Copied to Backport #62102: quincy: Quincy and pacific fail to compile after Boost upgrade of main added
- Copied to Backport #62103: pacific: Quincy and pacific fail to compile after Boost upgrade of main added
- Status changed from Fix Under Review to Pending Backport
- Backport deleted (
reef,quincy,pacific)
Cleared Backport field to avoid generating duplicate backport tickets -- Adam has created them manually.
- Status changed from Pending Backport to Resolved
- Status changed from Resolved to Pending Backport
- Tags set to backport_processed
- Status changed from Pending Backport to Resolved
Also available in: Atom
PDF