Skip to content

Conversation

xiaguan
Copy link
Collaborator

@xiaguan xiaguan commented Jul 25, 2025

Make release happy.

@@ -20,7 +20,7 @@ CPP_FILE=$(dirname $(readlink -f $0))/nvlink_allocator.cpp # get cpp file path,

# Use nvcc or g++ based on flag
if [ "$USE_NVCC" = true ]; then
nvcc "$CPP_FILE" -o "$OUTPUT_DIR/nvlink_allocator.so" -shared -Xcompiler -fPIC -lcuda -I/usr/local/cuda/include
nvcc "$CPP_FILE" -o "$OUTPUT_DIR/nvlink_allocator.so" -shared -Xcompiler -fPIC -I/usr/local/cuda/include
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Since we have CUDA in the env now, should we just use g++? The early compiled result of nvcc is not functioning well, not really sure about this version.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we didn't have full cuda support in ci. and we tried to remove cuda refs, which broke the release (the pr i reverted). so change this to make ci happy.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

But the release workload in https://github.com/kvcache-ai/Mooncake/blob/main/.github/workflows/release.yaml#L71C1-L75C90 will use nvcc and produce a nvlink_allocator.so which is not functioning as expected.

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.

2 participants