@spackbot run pipeline

I've started that pipeline for you!

@alalazo The change here didn't break the pipeline. I need to try to fix that PCH issue with %oneapi so we don't have to keep dealing with it on all of the Boost changes.

Can we work around that PCH issue for oneapi, until a proper fix is ready?

@spackbot run pipeline

I've started that pipeline for you!

@alalazo The Dyninst build failure in ci/gitlab-ci is a known issue and has been fixed in dyninst/master. We can merge here.

Ok, can you constrain the version of boost that dyninst can use in this PR, so that pipelines pass? After that this is mergeable.

Ok, can you constrain the version of boost that dyninst can use in this PR, so that pipelines pass? After that this is mergeable.

It's not a Boost issue, it's an STL one. Newer versions of gcc and clang have cleaned up the transitive includes of their STL headers. There are a couple of places in Dyninst that were affected by this.

It's not a Boost issue, it's an STL one. Newer versions of gcc and clang have cleaned up the transitive includes of their STL headers. There are a couple of places in Dyninst that were affected by this.

Do we know why this built in the first place then?¹ I'd like to double check why dyninst was ✔️ at some point, before force merging something that will break CI on develop.

@alalazo The pipeline stall here will be fixed by #35630

@spackbot run pipeline

I've started that pipeline for you!

@alalazo Boost 1.82.0 is coming out next week. This is working now, so we can merge. Thanks for the help!

Thanks @hainest !