From 68c2da30181f077ba99b9fbfedb2d4efe61fa9ee Mon Sep 17 00:00:00 2001 From: Faseel Chemmadan Date: Fri, 7 Aug 2026 14:31:14 +0200 Subject: [PATCH] updating faq with newer pixi way doing things --- docs/FAQ.md | 19 +++++++++++-------- 1 file changed, 11 insertions(+), 8 deletions(-) diff --git a/docs/FAQ.md b/docs/FAQ.md index 579c090c..5e6ebd24 100644 --- a/docs/FAQ.md +++ b/docs/FAQ.md @@ -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`.