Install

libc is distributed as a conda package that installs a precompiled Mojo package (libc.mojoc) into your environment's lib/mojo directory, so import libc resolves without extra flags.

pixi

pixi init -c https://conda.modular.com/max -c conda-forge -c https://prefix.dev/mojo-force .
pixi add libc

or, in pixi.toml:

[workspace]
channels = ["https://conda.modular.com/max", "conda-forge", "https://prefix.dev/mojo-force"]

[dependencies]
libc = ">=0.13.0,<0.14"
mojo = ">=1.1.0,<2"

conda / mamba

conda install -c https://conda.modular.com/max -c https://prefix.dev/mojo-force libc

The channel is a URL, and mojo-force on its own is not it

A bare channel name is read as an anaconda.org channel, so -c mojo-force asks conda.anaconda.org/mojo-force, which does not exist — and pixi reads "mojo-force" in channels the same way. The channel lives on prefix.dev, which is why both of the commands above spell it out. Written the short way the failure is a 404 for a channel that is not there, on a package that is.

From source

git clone https://github.com/mojothon/libc.git
cd libc
pixi run test            # run the test suite
pixi run package         # build dist/libc.mojoc

To consume a source checkout directly, point the compiler at src:

mojo run -I src your_program.mojo

Note

A precompiled .mojoc package is tied to the compiler version that produced it. Rebuild the package (or use the source checkout) after upgrading Mojo.