Re: [libre-riscv-dev] libre-riscv-dev Digest, Vol 23, Issue 16

[Luke Kenneth Casson Leighton <lkcl@lkcl.net>]

(cc'ing you direct, sam, as you're on "digest" mode.  if you make sure
to always cc yourself - and ask people at the top to cc you - it will
help people be able to reply to you much quicker, and you also won't
have to mess about cut/pasting the contents of the digest).

On Fri, Jul 10, 2020 at 9:47 PM Samuel Falvo II <sam.falvo@gmail.com> wrote:

> Just for grins, I tried with "cd nmigen && pip uninstall nmigen && pip
> install -e .", and it gave me this result:
>
> ERROR: nmigen-soc 0.0 has requirement nmigen~=0.1.rc1, but you'll have
> nmigen 0.3.dev134+g30e2f91 which is incompatible.

*click*.  that's it.  note "nmigen-soc".  you'll be able to see that
in nmigen-soc's setup.py.  (btw i cloned nmigen-soc in libre-soc.org
and *removed* that hard dependency version number.  don't use it
though because it's a hard fork of nmigen-soc).

you have a version of nmigen-soc installed (in the same virtualenv)
that DEMANDS nmigen 0.1, and exactly and ONLY nmigen 0.1.

you'll need to get rid of "nmigen-soc 0.0"... *BEFORE* you are
"permitted" to install the latest git of nmigen.

it sounds like setup.py has been modified to use pip3 by default.
that is a very worrying development and an extremely bad idea on the
part of the python developers.

samuel if you do actually use virtualenv, then so as to not disrupt
the kestrel and VDC development that you're doing, you might consider
setting up an entirely new virtualenv with a completely different
name.

i mean, it's what virtualenv is supposed to be for: create separate
completely isolated environments.  you might as well use it for that
:)

l.

_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev