fix: cuda 12.6 installation

[mickaelseznec]

Essential Elements of an Effective PR Description Checklist

• The purpose of the PR, such as "Fix some issue (link existing issues this PR will resolve)".
• The test plan, such as providing test command.
• The test results, such as pasting the results comparison before and after, or e2e results

Purpose

Fix #15435

Test Plan

CUDA 12.6 isn't used as default but might still be useful for some people. Not sure we want to add a CI check to this? I've tested locally, but if you want more testing, let me know what I should do 🙂

Test Result

[github-actions]

👋 Hi! Thank you for contributing to the vLLM project.

💬 Join our developer Slack at https://slack.vllm.ai to discuss your PR in #pr-reviews, coordinate on features in #feat- channels, or join special interest groups in #sig- channels.

Just a reminder: PRs would not trigger full CI run by default. Instead, it would only run fastcheck CI which starts running only a small and essential subset of CI tests to quickly catch errors. You can run other CI tests on top of those by going to your fastcheck build on Buildkite UI (linked in the PR checks section) and unblock them. If you do not have permission to unblock, ping simon-mo or khluu to add you in our Buildkite org.

Once the PR is approved and ready to go, your PR reviewer(s) can run CI to test the changes comprehensively before merging.

To run CI, PR reviewers can either: Add ready label to the PR or enable auto-merge.

🚀

[houseroad]

@huydhn , could you help review this one?

[houseroad]

I feel we can move most of the changes to some file like setup_utils.py, and only keep the call / override logic here to minimize the changes in the setup.py.

[LucasWilkinson]

I feel we can move most of the changes to some file like setup_utils.py, and only keep the call / override logic here to minimize the changes in the setup.py.

agreed; it'll be a bit easier to remove if this ever gets fixed

[LucasWilkinson]

LGTM! Thanks!

[mergify]

This pull request has merge conflicts that must be resolved before it can be
merged. Please rebase the PR, @mickaelseznec.

https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork