Open cbrnr opened 11 hours ago
It's not required -- I believe you can override with export CC=gcc
or similar when running a uv command.
Great, thanks! Yes, the CC
env variable overwrites the behavior. However, I don't know if it is desired that uv pip
behaves like pip
in this case; if so, it seems like either pip
has a different default (e.g. gcc
), or it tries multiple options (e.g. clang
, then gcc
). I would think that this is a useful behavior, but it is certainly also OK to just set the env varbiable.
I wanted to
uv pip install -e .
a local package which contains a C extension, but I received anerror: command 'clang' failed: No such file or directory
. Is this something thatuv
requires, or is it some upstream package (setuptools
maybe)? I'm asking because I already have a C compiler installed (cc
->gcc
), so maybe this can be changed with an environment variable? Also, installing the package with the OGpip
seems to usegcc
.