Build controls for AIX with xlclang and openxl toolchains

[tjcw]

Proposed changes

Supply build controls for AIX xlclang and openxl toolchains

Types of changes

What types of changes does your code introduce?

Put an x in the boxes that apply

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Code style update (formatting, renaming)
• Refactoring (no functional changes, no api changes)
• Documentation content changes
• Other (please describe):

Checklist

Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

• I searched the discussions
• I searched the closed and open issues
• I read the contribution guidelines
• I added myself to the copyright attributions for significant changes
• I checked that tests pass locally with my changes
• I added tests that prove my fix is effective or that my feature works
• I added necessary documentation (if appropriate)

Further comments

If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc...

[grafikrobot]

How is this different than #421 ??

[tjcw]

This PR is different from #421 . This one introduces support for openxl and xlclang tool chains on AIX . #421 works around a deficiency in AIX directory name support.

[tjcw]

I see the test fails with messages

src/tools/openxl.jam has documentation but is not included anywhere, uses tags: doc
src/tools/xlclang.jam has documentation but is not included anywhere, uses tags: doc

Please can someone tell me how to link these into the documentation system to get the tests to pass. Thanks !

[grafikrobot]

Please can someone tell me how to link these into the documentation system to get the tests to pass. Thanks !

It means they need to get added to the reference doc in the right section.. https://github.com/bfgroup/b2/blob/main/doc/src/reference.adoc

[tjcw]

How is this different than #421 ??

I have closed #421 as not being required. I think this one is now ready for review and removing the 'draft' label.

[tjcw]

I have added the files as required

[tjcw]

So is the failing check related to the change?
You should be able to look at the patch and verify that it only changes things for xlclang and openxl tool chains , i.e. it is only an AIX change and you do not have any AIX tests.

Something caused a test to run for an hour until cancelled, but I don't think my change did it.

What next ?

[grafikrobot]

So is the failing check related to the change? You should be able to look at the patch and verify that it only changes things for xlclang and openxl tool chains , i.e. it is only an AIX change and you do not have any AIX tests.

Something caused a test to run for an hour until cancelled, but I don't think my change did it.

It's a recurring problem that I haven't been able to track down (as it only happens in CI). I'm rerunning the checks.

What next ?

Here's the thing.. I'm unhappy with yet more toolsets for the IBM compilers. As they are all almost identical. Ideally we would have just one toolset that handles the variation internally. I started sketching out such a toolset a few days ago. But it's going to take some time for me to get it sufficiently complete to test (as I have ISO WG21 meetings this week). Would you be able to test and help out further tweaking of such a combined toolset?

[tjcw]

Yes, I can help with that. Just tell me which repo to clone and what command to run.

[tjcw]

I will need to ask my manager whether I can run your code on my IBM owned AIX box. If the answer is no, then the boost project could buy the usage you need in the IBM cloud here https://cloud.ibm.com/power/overview . I think there are also possibilities on university-owned machines but I don't have a reference to hand.

[tjcw]

Take a look at https://community.ibm.com/community/user/powerdeveloper/blogs/linda-alkire-kinnunen/2022/08/08/accelerate-your-open-source-development-with-acces ; in particular the IBM Technology Zone. This grants access for 2 weeks at a time, extendable to 4 weeks, to AIX systems at no charge; which sounds like exactly the access you need for your testing.
My manager was out sick today so I haven't been able to ask him whether your prototype b2 code would be allowed on my IBM AIX system. I can't see it being a problem, because I am generally allowed to use any open source code I can get my hands on (IBM is pickier about what it will distribute integrated into an IBM product) and I take it you will make the prototype code available under the same terms as the main BOOST code. But I do have to ask.

[grafikrobot]

Take a look at https://community.ibm.com/community/user/powerdeveloper/blogs/linda-alkire-kinnunen/2022/08/08/accelerate-your-open-source-development-with-acces ; in particular the IBM Technology Zone. This grants access for 2 weeks at a time, extendable to 4 weeks, to AIX systems at no charge; which sounds like exactly the access you need for your testing.

I have access to the GCC compile farm. Which includes 2 AIX machines. But I haven't had time to check if they have the IBM compilers installed (doing triple duty this week with wg21 meeting going on). But if the gcc farm doesn't have the compilers the above sounds like it could work out.

My manager was out sick today so I haven't been able to ask him whether your prototype b2 code would be allowed on my IBM AIX system. I can't see it being a problem, because I am generally allowed to use any open source code I can get my hands on (IBM is pickier about what it will distribute integrated into an IBM product) and I take it you will make the prototype code available under the same terms as the main BOOST code. But I do have to ask.

It's just going to be a branch in the regular B2 repo (i.e. here) with the regular Boost license. And technically will be a consolidation of the two existing toolsets and your two toolsets into a single ibmcxx.jam file.

[tjcw]

I'm told that Sangamesh Mallayya, [email protected], manages AIX systems at OSU which are available for open source development. Let him know that you need xlC, openxl, and ibmclang compilers installed and you should be good to go.

[tjcw]

Power ISV Lab Questionnaire - New ISV.docx
Here is a form to request access to an AIX system in Poughkeepsie, NY. If you want access there, fill in the details and send it back to me ( [email protected] )

[tjcw]

Good news

My manager has given the ok for me to take your prototype open source code and run it on the AIX machine I have access to.

[grafikrobot]

Good news

My manager has given the ok for me to take your prototype open source code and run it on the AIX machine I have access to.

Awesome. I got back to working on this yesterday and it's progressing okay. Hope to have something ready by the weekend.

I might still try the gcc compile farm AIX systems as a quick check. :-)