This repository was archived by the owner on Jan 5, 2026. It is now read-only.
Description I'm guessing you've fixed something to do with the Git submodules that is still present in the latest tag you have available.
Collecting misoc (from -r requirements.txt (line 3))
Cloning https://github.com/m-labs/misoc (to revision 0.12) to /tmp/pip-install-1whmjgce/misoc_10587c2327dd468cb9ae015eb90c3230
Running command git clone --filter=blob:none --quiet https://github.com/m-labs/misoc /tmp/pip-install-1whmjgce/misoc_10587c2327dd468cb9ae015eb90c3230
Running command git checkout -q 714ea6899b038c07b5a20f02a2172496486f9ef0
Resolved https://github.com/m-labs/misoc to commit 714ea6899b038c07b5a20f02a2172496486f9ef0
Running command git submodule update --init --recursive -q
fatal: unable to access 'http://llvm.org/git/compiler-rt.git/': Maximum (20) redirects followed
fatal: clone of 'http://llvm.org/git/compiler-rt.git' into submodule path '/tmp/pip-install-1whmjgce/misoc_10587c2327dd468cb9ae015eb90c3230/misoc/software/compiler_rt' failed
Failed to clone 'misoc/software/compiler_rt'. Retry scheduled
fatal: unable to access 'http://llvm.org/git/libunwind.git/': Maximum (20) redirects followed
fatal: clone of 'http://llvm.org/git/libunwind.git' into submodule path '/tmp/pip-install-1whmjgce/misoc_10587c2327dd468cb9ae015eb90c3230/misoc/software/unwinder' failed
Failed to clone 'misoc/software/unwinder'. Retry scheduled
fatal: unable to access 'http://llvm.org/git/compiler-rt.git/': Maximum (20) redirects followed
fatal: clone of 'http://llvm.org/git/compiler-rt.git' into submodule path '/tmp/pip-install-1whmjgce/misoc_10587c2327dd468cb9ae015eb90c3230/misoc/software/compiler_rt' failed
Failed to clone 'misoc/software/compiler_rt' a second time, aborting
error: subprocess-exited-with-error
Installing from master doesn't have this issue. Do you need to create a new tag that incorporates whatever the fix is?
Reactions are currently unavailable
I'm guessing you've fixed something to do with the Git submodules that is still present in the latest tag you have available.
Installing from
masterdoesn't have this issue. Do you need to create a new tag that incorporates whatever the fix is?