Skip to content
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.

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

meson.build: ensure the project git directory is used #544

Open
wants to merge 1 commit into
base: bleeding
Choose a base branch
from

meson.build: ensure the project git directory is used

733c266
Select commit
Loading
Failed to load commit list.
Open

meson.build: ensure the project git directory is used #544

meson.build: ensure the project git directory is used
733c266
Select commit
Loading
Failed to load commit list.
Cirrus CI / MacOS failed Jun 3, 2024 in 22s

Task Summary

Instruction setup failed in 00:19

Details

⚠️ Not enough compute credits to prioritize tasks!

✅ 00:01 clone
❌ 00:19 setup

🍺  /opt/homebrew/Cellar/libffi/3.4.6: 18 files, 764.4KB
==> Pouring libgit2--1.7.2.arm64_ventura.bottle.tar.gz
🍺  /opt/homebrew/Cellar/libgit2/1.7.2: 105 files, 4.5MB
==> Pouring nanomsg--1.2.arm64_ventura.bottle.tar.gz
🍺  /opt/homebrew/Cellar/nanomsg/1.2: 26 files, 389.6KB
==> Caveats
==> meson
zsh completions have been installed to:
  /opt/homebrew/share/zsh/site-functions
==> libffi
libffi is keg-only, which means it was not symlinked into /opt/homebrew,
because macOS already provides this software and installing another version in
parallel can cause all kinds of trouble.

For compilers to find libffi you may need to set:
  export LDFLAGS="-L/opt/homebrew/opt/libffi/lib"
  export CPPFLAGS="-I/opt/homebrew/opt/libffi/include"

For pkg-config to find libffi you may need to set:
  export PKG_CONFIG_PATH="/opt/homebrew/opt/libffi/lib/pkgconfig"
sudo pip3 install cram==0.7
WARNING: The directory '/Users/admin/Library/Caches/pip' or its parent directory is not owned or is not writable by the current user. The cache has been disabled. Check the permissions and owner of that directory. If executing pip with sudo, you should use sudo's -H flag.
error: externally-managed-environment

× This environment is externally managed
╰─> To install Python packages system-wide, try brew install
    xyz, where xyz is the package you are trying to
    install.
    
    If you wish to install a Python library that isn't in Homebrew,
    use a virtual environment:
    
    python3 -m venv path/to/venv
    source path/to/venv/bin/activate
    python3 -m pip install xyz
    
    If you wish to install a Python application that isn't in Homebrew,
    it may be easiest to use 'pipx install xyz', which will manage a
    virtual environment for you. You can install pipx with
    
    brew install pipx
    
    You may restore the old behavior of pip by passing
    the '--break-system-packages' flag to pip, or by adding
    'break-system-packages = true' to your pip.conf file. The latter
    will permanently disable this error.
    
    If you disable this error, we STRONGLY recommend that you additionally
    pass the '--user' flag to pip, or set 'user = true' in your pip.conf
    file. Failure to do this can result in a broken Homebrew installation.
    
    Read more about this behavior here: <https://peps.python.org/pep-0668/>

note: If you believe this is a mistake, please contact your Python installation or OS distribution provider. You can override this, at the risk of breaking your Python installation or OS, by passing --break-system-packages.
hint: See PEP 668 for the detailed specification.
�����������������