charlesbluca opened a new pull request, #438:
URL: https://github.com/apache/arrow-datafusion-python/pull/438
# Which issue does this PR close?
<!--
We generally require a GitHub issue to be filed for all bug fixes and
enhancements and this helps us generate change logs for our releases. You can
link an issue to this PR using the GitHub syntax. For example `Closes #123`
indicates that this PR will close issue #123.
-->
n/a
# 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.
-->
Our conda nightly builds emit some warnings around overlinking:
```
WARNING
(datafusion,lib/python3.11/site-packages/datafusion/_internal.abi3.so): Needed
DSO lib/liblzma.so.5 found in ['xz']
WARNING
(datafusion,lib/python3.11/site-packages/datafusion/_internal.abi3.so): .. but
['xz'] not in reqs/run, (i.e. it is overlinking) (likely) or a missing
dependency (less likely)
WARNING
(datafusion,lib/python3.11/site-packages/datafusion/_internal.abi3.so): Needed
DSO lib/libgcc_s.so.1 found in ['libgcc-ng']
WARNING
(datafusion,lib/python3.11/site-packages/datafusion/_internal.abi3.so): .. but
['libgcc-ng'] not in reqs/run, (i.e. it is overlinking) (likely) or a missing
dependency (less likely)
```
That seem to be due to leaving out some build/host requirements that should
be explicitly specified. This PR does this using the same approach taken in
https://github.com/conda-forge/staged-recipes/pull/23386 to resolve overlinking
issues in a similar maturin project.
# What changes are included in this PR?
<!--
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.
-->
Adds Rust / C compilers to build deps to resolve the `libgcc_s.so.1`
dependency, and `xz` to the host deps to resolve the `liblzma.so.5` dependency
# Are there any user-facing changes?
<!--
If there are user-facing changes then we may require documentation to be
updated before approving the PR.
-->
n/a
<!--
If there are any breaking changes to public APIs, please add the `api
change` label.
-->
--
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]