linkedin / linkedin/Liger-Kernel

Issue while building from source on ROCM

Open
#538 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
6.6k
Forks
603
Avg merge
1d 20h
Merged PRs (30d)
47

Description

### 🐛 Describe the bug

Getting an error when I try to build from source on ROCM

### Reproduce

```
pip install torch torchvision torchaudio --index-url https://download.pytorch.org/whl/rocm6.2

git clone https://github.com/linkedin/Liger-Kernel.git
pip install -e .
```

results in

```
Installing build dependencies ... done
Checking if build backend supports build_editable ... done
Getting requirements to build editable ... done
Preparing editable metadata (pyproject.toml) ... done
INFO: pip is looking at multiple versions of liger-kernel to determine which version is compatible with other requirements. This could take a while.
ERROR: Could not find a version that satisfies the requirement torch>=2.6.0.dev (from liger-kernel) (from versions: 1.11.0, 1.12.0, 1.12.1, 1.13.0, 1.13.1, 2.0.0, 2.0.1, 2.1.0, 2.1.1, 2.1.2, 2.2.0, 2.2.1, 2.2.2, 2.3.0, 2.3.1, 2.4.0, 2.4.1, 2.5.0, 2.5.1)
ERROR: No matching distribution found for torch>=2.6.0.dev
```

### Versions

```
Environment Report:
-------------------
Operating System: Linux-5.15.0-116-generic-x86_64-with-glibc2.35
Python version: 3.10.0
Liger Kernel: Not installed
PyTorch version: 2.5.1+rocm6.2
CUDA version: None
HIP(ROCm) version: 6.2.41133-dd7f95766
Triton version: 3.1.0
Transformers: Not installed
XPU version: XPU Not Available
```

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing `pip install -e .` with the ROCm 6.2 and PyTorch 2.5.1 environment shown. Inspect `pyproject.toml` and the editable-install dependency metadata to understand the `torch>=2.6.0.dev` requirement. Done means the source install resolves dependencies successfully on the reported ROCm setup.

Written by the indexing model from the issue text.

Assessment

Tech stack
linux, python, pytorch
Domain
build-system
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.