search

Chia-Network / chia-dev-tools

A utility for developing in the Chia ecosystem: Chialisp functions, object inspection, RPC client and more.
Apache License 2.0
45 stars 32 forks source link

'pip install chia-dev-tools' error #27

Closed ikang9712 closed 2 years ago

ikang9712 commented 2 years ago

Hello!

I cloned https://github.com/Chia-Network/chia-dev-tools/commit/8430a75f49b863142aa5b1354e60454acb017f87 and activated pyenv and typed `pip install chia-dev-tools'.

Then I got this error message. I tried reinstalling pip, reinstall the problematic package via the given link, but still got an error. Thank you!! :)

Screen Shot 2022-02-04 at 5 26 01 PM
matholamew commented 2 years ago

I am having the same problem. Are you on an M1 Mac by any chance? I don't have any resolution, I'm just trying to bring this back up to anyone who may be able to help.

Quexington commented 2 years ago

Try installing the latest version and try again. I think there was a potential bug in that version of chia-blockchain that may have led to this.

Quexington commented 2 years ago

I haven't gotten any response on this so I'm going to close it.

Ganbin commented 1 year ago

I had the same issue on my Apple M1. I have followed this video and it solved my issue python environment setup on Apple Silicon | M1, M1 Pro/Max with Conda-forge

fede2442 commented 1 year ago

I had this issue at some point while trying to install chia-dev-tools and I was fighting all day with it. For this particular issue what i did is follow that error and install rust and cargo which solved this issue.

I have a macbook pro m1 2022. And after this error was fixed I faced the following issue for a long long time:

image

I tried everything and the only thing that worked was installing miniforge (https://github.com/conda-forge/miniforge) and creating a virtual environment with that, which creates a arm64 one. Inside the base env created with conda I was able to just run pip install chia-dev-tools and even though I got an error all tools installed correctly.

this video was the life saver: https://www.youtube.com/watch?v=2Acht_5_HTo

There is clearly an issue with M1 macs.