Conversation
| ]; | ||
| sourceBuild = true; | ||
| } | ||
| #{ |
There was a problem hiding this comment.
Disabled, because we are now CUDA 12.6+.
| #{ | ||
| # torchVersion = "2.8"; | ||
| # cudaVersion = "12.4"; | ||
| # cxx11Abi = true; | ||
| # systems = [ | ||
| # "x86_64-linux" | ||
| # "aarch64-linux" | ||
| # ]; | ||
| # sourceBuild = true; | ||
| #} |
There was a problem hiding this comment.
Yeah, see my comment above. We now only have CUDA 12.6 and up. Which means we finally have to make FA3 work with a newer CUDA version.
| lib.optionalString metalSupport '' | ||
| METAL_PATH=$(${xcrunHost}/bin/xcrunHost xcodebuild -showComponent MetalToolchain 2> /dev/null | sed -rn "s/Toolchain Search Path: (.*)/\1/p") | ||
| if [ ! -d "$METAL_PATH" ]; then | ||
| >&2 echo "Cannot find Metal toolchain, use: xcodebuild -downloadComponent MetalToolchain" | ||
| exit 1 | ||
| fi |
There was a problem hiding this comment.
if the user building the kernel don't have MetalToolchain installed would it be better to use downloadComponent and get the toolchain and the path or just raise an error ?
There was a problem hiding this comment.
I am not very keen on modifying the user's development environment outside the sandbox. Also, it will only result in half an install, because the toolchain mapping for the user is not set up (since the build runs as a non-privileged user).
Co-authored-by: Mohamed Mekkouri <93391238+MekkCyber@users.noreply.github.com>
|
Some kernel are failing on Metal 3 when compile with Metal 4 (which is now the default for kernel-builder) Any idea how to solve ? |
3 participants
Uh oh!
There was an error while loading. Please reload this page.