sjperkins opened a new pull request, #33805:
URL: https://github.com/apache/arrow/pull/33805
Closes #33804
<!--
Thanks for opening a pull request!
If this is your first pull request you can find detailed information on how
to contribute here:
* [New Contributor's
Guide](https://arrow.apache.org/docs/dev/developers/guide/step_by_step/pr_lifecycle.html#reviews-and-merge-of-the-pull-request)
* [Contributing
Overview](https://arrow.apache.org/docs/dev/developers/overview.html)
If this is not a [minor
PR](https://github.com/apache/arrow/blob/master/CONTRIBUTING.md#Minor-Fixes).
Could you open an issue for this pull request on GitHub?
https://github.com/apache/arrow/issues/new/choose
Opening GitHub issues ahead of time contributes to the
[Openness](http://theapacheway.com/open/#:~:text=Openness%20allows%20new%20users%20the,must%20happen%20in%20the%20open.)
of the Apache Arrow project.
Then could you also rename the pull request title in the following format?
GH-${GITHUB_ISSUE_ID}: [${COMPONENT}] ${SUMMARY}
or
MINOR: [${COMPONENT}] ${SUMMARY}
In the case of PARQUET issues on JIRA the title also supports:
PARQUET-${JIRA_ISSUE_ID}: [${COMPONENT}] ${SUMMARY}
-->
### Rationale for this change
<!--
Why are you proposing this change? If this is already explained clearly in
the issue then this section is not needed.
Explaining clearly why changes are proposed helps reviewers understand your
changes and offer better suggestions for fixes.
-->
At some point, it would be useful to support the new C++ ABI
`_GLIBCXX_USE_CXX11_ABI=1`, especially when moving to C++17:
- https://github.com/apache/arrow/issues/32415
I wanted to create a pyarrow wheel that supported the above ABI and adapted
the existing CENTOS 7 manylinux2014 Dockerfile/wheel to produce a AlmaLinux 8
manylinux_2_28 Dockerfile/wheel.
Publishing wheels with a new ABI needs [careful
consideration](https://pypackaging-native.github.io/key-issues/native-dependencies/cpp_deps/)
so I think this is low priority, but I thought I'd provide this manylinux_2_28
implementation in case it was useful for current/future adoption.
### What changes are included in this PR?
A manylinux_2_28 Dockerfile, adopted from the existing manylinux2014
Dockerfile
<!--
There is no need to duplicate the description in the issue here but it is
sometimes worth providing a summary of the individual changes in this PR.
-->
### Are these changes tested?
Manually tested at present
### Are there any user-facing changes?
Yes, there's a major ABI change, as pyarrow will be compiled with
`_GLIBCXX_USE_CXX11_ABI=1`
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
