Skip to content

Commit b23dc4c

Browse files
authored
Merge pull request #136 from faseelmo/feature/faq_pixi_dependency_issue
updating faq with how to solve pixi system requirements isues
2 parents c496fc3 + 27f4d80 commit b23dc4c

1 file changed

Lines changed: 14 additions & 0 deletions

File tree

docs/FAQ.md

Lines changed: 14 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -66,3 +66,17 @@ In most cases those should be already installed in your system, but in case they
6666
- Debian/Ubuntu-based distributions: `sudo apt-get install libgl1-mesa-dri libglx-mesa0 libegl-mesa0`
6767
- Fedora-based distributions: `sudo dnf install mesa-libGL mesa-libEGL mesa-dri-drivers`
6868

69+
### What to do if pixi fails to solve the environment due to system requirements (e.g., __glibc)?
70+
71+
When adding packages, you might get dependency conflicts containing an error like `└─ __glibc >=2.34,<3.0.a0, for which no candidates were found`.
72+
73+
You can fix this by explicitly defining your system's actual capabilities in your pixi.toml file.
74+
Add or update the `[system-requirements]` section to include your required baseline:
75+
76+
```toml
77+
[system-requirements]
78+
libc = { family = "glibc", version = "2.31" }
79+
linux = "5.15"
80+
```
81+
82+
Note: Set the glibc version to match the oldest machine or robot that needs to run your project, not necessarily your personal machine. You can check a machine's version by running `ldd --version`.

0 commit comments

Comments
 (0)