You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When installing boost with Intel oneAPI using the recommended way (bootstrap), the compiler gives the following warning
These options as listed are not supported.
For more information, use '-qnextgen-diag'.
option list:
-ip
-wd177,780,2196,1782,193,304,981,1418,411,734,279
As far as I can see, Boost.Build does not discriminate between the legacy Intel compiler and the newer LLVM-based one - both are identified as intel-linux (on Linux platform). So there is no way I could add these flags for the legacy compiler but not the newer one.
I can see you've already created an issue for b2 to support the new compiler. Until that issue is resolved, there's nothing I can do in Boost.Log.
In the meantime, you can patch your local Boost by removing the compiler options that don't work.
yes, unfortunately the PR at b2 is stuck because there is no test setup for Intel compilers.
As far as I see, the flags specific to boost.log only disable warnings. So my suggestion would be to simply remove them to reverse the behavior: Instead of showing warnings for new compiler versions, show (other) warnings for old compiler versions. Unfortunately, one would still get the warning about -ip which is caused by b2.
Activity
Lastique commentedon Feb 22, 2025
As far as I can see, Boost.Build does not discriminate between the legacy Intel compiler and the newer LLVM-based one - both are identified as
intel-linux(on Linux platform). So there is no way I could add these flags for the legacy compiler but not the newer one.I can see you've already created an issue for
b2to support the new compiler. Until that issue is resolved, there's nothing I can do in Boost.Log.In the meantime, you can patch your local Boost by removing the compiler options that don't work.
MarDiehl commentedon Feb 22, 2025
yes, unfortunately the PR at
b2is stuck because there is no test setup for Intel compilers.As far as I see, the flags specific to
boost.logonly disable warnings. So my suggestion would be to simply remove them to reverse the behavior: Instead of showing warnings for new compiler versions, show (other) warnings for old compiler versions. Unfortunately, one would still get the warning about-ipwhich is caused byb2.