-
-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Switch to cross-compilation for linux_aarch64
and linux_ppc64le
#25
Comments
This was referenced Apr 5, 2024
Merged
Switch to cross-compilation for
linux_aarch64
and linux_ppc64le
conda-forge/cuda-cudart-feedstock#25
Merged
Merged
Merged
Merged
Merged
Switch to cross-compilation for
linux_aarch64
and linux_ppc64le
conda-forge/cuda-nvprune-feedstock#7
Merged
Merged
Merged
Merged
Closed
Merged
Merged
Merged
Switch to cross-compilation for
linux_aarch64
and linux_ppc64le
conda-forge/libcusparse-feedstock#13
Merged
Merged
Switch to cross-compilation for
linux_aarch64
and linux_ppc64le
conda-forge/libcusolver-feedstock#15
Merged
Merged
Merged
This was referenced Apr 10, 2024
Merged
Closing as completed |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Sometimes the natives builds of
linux_aarch64
andlinux_ppc64le
on Travis CI don't start or fail in the queuing process, which needs restarting. This creates a bit of friction during the CTK release processTo reduce this friction, think we should switch
linux_aarch64
andlinux_ppc64le
to "cross-compilation" on Azure. As the CTK packages are binary redists, we are not actually cross-compiling them. However the way the build architecture for Azure is setup is to use cross-compilers and differentbuild_platform
andtarget_platform
. This would allow the builds to complete just as fast. Though it would mean that some kinds of tests (like running binaries for thetarget_platform
) wouldn't work in cross-compilation (as they do in the native case). However this can already be an issue as we don't currently test with GPUs eitherMaking this change would amount to adding the following lines to the top of
conda-forge.yml
files for the feedstocks and re-rendering:The text was updated successfully, but these errors were encountered: