-
Notifications
You must be signed in to change notification settings - Fork 195
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
boost (v1.71.0) #1035
Comments
boostorg/mpi#81 which has been landed in v1.71.0 release (#1035) Signed-off-by: Karl W. Schulz <[email protected]>
https://src.fedoraproject.org/rpms/boost/raw/master/f/boost-1.66.0-bjam-build-flags.patch which touches file not present in v1.71.0 (#1035) Signed-off-by: Karl W. Schulz <[email protected]>
…ntel (#1035) Signed-off-by: Karl W. Schulz <[email protected]>
…1035) Signed-off-by: Karl W. Schulz <[email protected]>
@amblakem I'm having trouble getting the latest Boost release to build with the Intel toolchain. gcc variant is building but I'm getting something with intel that I don't recall seeing before (and a web search hasn't turned up anything for met yet). This issue is the initial bootstrap fails complaining about needing a C+=11 feature. I tried to enable by setting Example message is pasted below. Can you possibly take a look and see if you can get a build to cooperate with recent parallel studio? (I'm using 2019.u5 in OBS presently).
|
Sure thing. I'll take a look and report back. |
Thanks. |
…nhpc#1035) Signed-off-by: Aaron Blakeman <[email protected]>
I just put in a PR with a proposed fix. It looks like you were on the right track with what needed fixed, thank you for the pointers. There is an upstream issue tracking this (boostorg/build#475) I believe that travis is failing on my PR because of #1034. |
supplied by Aaron which touches the intel-linux toolset directly (#1035) Signed-off-by: Karl W. Schulz <[email protected]>
Thanks for the sleuthing - i missed the upstream tracker. Looks like all of the builds are completing now with intel toolchain. |
Tests passing in CI. |
http://www.boost.org/
The text was updated successfully, but these errors were encountered: