[libre-riscv-dev] Dumb question time with Sam

[libre-riscv-dev] Dumb question time with Sam

[Samuel Falvo II]

I'm attempting to run "make test" with the soc.git repo, and it's just not
working.  I suspect I managed to botch my environment configuration
somehow.  This is the first occurrence of an error; there may be others,
but this is far and above the most prominent error I see in the output:

Failure: ImportError (cannot import name 'Settle' from 'nmigen.back.pysim'
(/home/kc5tja/git/libre-soc/env3/lib/python3.8/site-packages/nmigen-0.1-py3.8.egg/nmigen/back/pysim.py))
... ERROR

The nmigen in question was just downloaded last night.  Can anyone else
confirm this is a legit issue with either my setup, with nmigen, or
otherwise know how to work around this?

Thanks.

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

Re: [libre-riscv-dev] Dumb question time with Sam

[Luke Kenneth Casson Leighton]

On Fri, Jul 10, 2020 at 4:58 PM Samuel Falvo II <sam.falvo@gmail.com> wrote:
>
> I'm attempting to run "make test" with the soc.git repo,

yyeah that will get you into a world of pain :)  i'm doing my best to
keep the unit tests up-to-date however there's simply too much for
only one full-time person to do.


> and it's just not
> working.  I suspect I managed to botch my environment configuration
> somehow.  This is the first occurrence of an error; there may be others,
> but this is far and above the most prominent error I see in the output:
>
> Failure: ImportError (cannot import name 'Settle' from 'nmigen.back.pysim'
> (/home/kc5tja/git/libre-soc/env3/lib/python3.8/site-packages/nmigen-0.1-py3.8.egg/nmigen/back/pysim.py))

0.1.  that's out-of-date.  we specifically work with the git versions,
not with old releases.  the HDL_workflow instructions - and the
dev-setup scripts - would contain that exact version (and command to
install it), if we were using it.

this is why i sent you a (private) message containing the git
repositories to clone, and pointed you at the HDL_workflow.  section
on nmigen:

mkdir ~/src
cd !$
git clone https://github.com/nmigen/nmigen.git
cd nmigen
sudo bash
python3 setup.py develop
ctrl-d

notice several things:

1. glt clone development version
2. no mention of "pip3"
3. no mention of "virtualenv"
4. use of python3 setup.py >>>>DEVELOP<<<< *NOT* python3 setup.py >>INSTALL<<

if you absolutely insist on using pip3, the same effect as python3
setup.py develop can i believe be achieved with something like "pip3
install ." (notice and observe that the fullstop there is not a
sentence fullstop, it is part of the command and represents the
current working directory).

i really do not like pip3 due to the security implications (no GPG
signing of packages, no web of trust, pypi.org website becomes a
high-priority phishing and hacking target *yes this has actually
happened*) as it results in arbitrary untrusted code download and
execution.

anyway.

yes.

use latest clone, not v0.1.  it's guaranteed not to work.

l.

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

Re: [libre-riscv-dev] Dumb question time with Sam

[Tobias Platen]

I head similar errors one week ago, and I did not yet find a way to resolve those.

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

Re: [libre-riscv-dev] Dumb question time with Sam

[Luke Kenneth Casson Leighton]

On Friday, July 10, 2020, Tobias Platen <libre-soc@platen-software.de>
wrote:

> I head similar errors one week ago, and I did not yet find a way to
> resolve those.


don't use nmigen 0.1

l.



-- 
---
crowd-funded eco-conscious hardware: https://www.crowdsupply.com/eoma68
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

Re: [libre-riscv-dev] Dumb question time with Sam

[Luke Kenneth Casson Leighton]

On Friday, July 10, 2020, Luke Kenneth Casson Leighton <lkcl@lkcl.net>
wrote:

>
>
> On Friday, July 10, 2020, Tobias Platen <libre-soc@platen-software.de>
> wrote:
>
>> I head similar errors one week ago, and I did not yet find a way to
>> resolve those.
>
>
> don't use nmigen 0.1
>

also if you are updating (git pull) it is imperative to re-run setup.py
develop.

l.




-- 
---
crowd-funded eco-conscious hardware: https://www.crowdsupply.com/eoma68
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

Re: [libre-riscv-dev] Dumb question time with Sam

[Luke Kenneth Casson Leighton]

also, to both of you: if you've installed nmigen 0.1 globally you
might need to hunt it down and kill it.  python3 -v followed by
"import nmigen" is your friend, there, as it will show exactly where
things are imported from.

if that really doesn't show you the location then use strace, which
tracks every system call.

l.

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