Skip to content

updating faq with newer pixi way doing things #145

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
faseelmo wants to merge 1 commit into
base: main
Choose a base branch
from
+11 −8
Open

updating faq with newer pixi way doing things #145

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 11 additions & 8 deletions docs/FAQ.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -68,15 +68,18 @@ In most cases those should be already installed in your system, but in case they

### What to do if pixi fails to solve the environment due to system requirements (e.g., __glibc)?

When adding packages, you might get dependency conflicts containing an error like `└─ __glibc >=2.34,<3.0.a0, for which no candidates were found`.
When adding packages, you might get dependency conflicts like:

You can fix this by explicitly defining your system's actual capabilities in your pixi.toml file.
Add or update the `[system-requirements]` section to include your required baseline:
```bash
└─ __glibc >=2.34,<3.0.a0, for which no candidates were found.
```

You can fix this by explicitly defining your system's actual capabilities in your pixi.toml file.
Update the `workspace.platforms` section to include your required baseline like shown below. See [pixi docs](https://pixi.prefix.dev/latest/workspace/multi_platform_configuration/#declaring-virtual-packages-per-platform) for more info.

```toml
[system-requirements]
libc = { family = "glibc", version = "2.31" }
linux = "5.15"
[workspace]
platforms = [
{ name="rover", platform = "linux-64", glibc = "2.39"}
]
```

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`.