Closed gojimmypi closed 5 years ago
These github riscv packages are maintained by a lot of different people, and getting everyone to agree on one convention is infeasible. Also, a lot of the people working with these projects don't fully understand how git submodules work. They just use them. When I find ssh: references I fix them, but I'm not going to worry about https versus git. Using insteadOf is what we recommend when people run into trouble.
FYI This project is not being actively maintained at present. I would suggest using upstream qemu instead of this one, unless perhaps you need the support for separate bbl/vmlinux which is only here at the moment, though we are trying to get it upstream. All of the real riscv qemu work is happening upstream now.
understood. thanks
Some firewalls will block ports used by
git://
withgit clone
returning an unintuitiveerrno=Connection refused
error message like this:One possible solution:
git config --global url.https://github.com/riscv.insteadOf git://github.com/riscv
I'm curious: why not always use
https://
?edit: see also: https://github.com/cliffordwolf/picorv32/issues/106