Conversation
|
I assume this is dependent on boostorg/build#778, which should presumably be re-issued against the upstream https://github.com/bfgroup/b2? |
|
I raised the PR on the repository where the affected files were. Should I raise an issue in the b2 repository pointing to this PR ? |
|
If you're asking whether you need to open a pull request in https://github.com/bfgroup/b2, the answer is yes, that's the main repository for b2 nowadays. boostorg/build is updated regularly from bfgroup/b2. |
|
OK, raised in that repo as bfgroup/b2#421 |
|
No, that's not what I meant. The changes to b2 in boostorg/build#778 need to be raised against bfgroup/b2, not the Boost-specific bootstrap changes. |
|
OK, raised as bfgroup/b2#422 |
|
The tests that failed were not due to the code change in this PR. One test timed out at 60 minutes, presumably because MSVC was slow. The other 2 failures were environment-related; the test needed a zip/unzip command which was unable to be installed. Please retest as appropriate. |
|
Yes, I knew that these failures weren't caused by the change in this PR. They were caused by problems in Log and Iostreams, which have been now fixed. But I don't think there's any need to merge this PR before the changes to b2, because without them, the b2 toolset can never be |
This PR adds support for openxl and xlclang toolchains on AIX