Skip to content
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

Provide Target machine architecture for cross-compile scenarios. #21780

Merged
merged 1 commit into from
Jan 27, 2025

Conversation

copybara-service[bot]
Copy link

@copybara-service copybara-service bot commented Jan 23, 2025

Provide Target machine architecture for cross-compile scenarios.

CUDA/CUDNN/NCCL repositories are created on a host machine, so if we need to download redistributions for other architectures in cross-compile scenario, we need to pass the target architecture name to repo rules, e.g. --repo_env=CUDA_REDIST_TARGET_PLATFORM=aarch64

@copybara-service copybara-service bot force-pushed the test_719020277 branch 2 times, most recently from afd01d2 to 7fc0c06 Compare January 27, 2025 16:44
@copybara-service copybara-service bot changed the title Add ability to pass custom architecture name to CUDA/CUDNN/NCCL repo rules. Provide Target machine architecture for cross-compile scenarios. Jan 27, 2025
@copybara-service copybara-service bot force-pushed the test_719020277 branch 4 times, most recently from 5928fd0 to 511bb67 Compare January 27, 2025 19:31
CUDA/CUDNN/NCCL repositories are created on a host machine, so if we need to download redistributions for other architectures in cross-compile scenario, we need to pass the target architecture name to repo rules, e.g. `--repo_env=CUDA_REDIST_TARGET_PLATFORM=aarch64`

PiperOrigin-RevId: 720254498
@copybara-service copybara-service bot merged commit 7ad64b5 into main Jan 27, 2025
1 check passed
@copybara-service copybara-service bot deleted the test_719020277 branch January 27, 2025 20:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant