From: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
To: Libre-RISCV General Development <libre-riscv-dev@lists.libre-riscv.org>
Subject: Re: [libre-riscv-dev] Dumb question time with Sam
Date: Fri, 10 Jul 2020 17:10:17 +0100
Message-ID: <CAPweEDxwWcbfvA331z0RkOdAfyUaDcGws+=JCF-OoidS6_f9SQ@mail.gmail.com> (raw)
In-Reply-To: <CAEz=sokHWn3uFgomWRLXUDwmtO7dKXcj0rvi1yxSe5zN7YFKUg@mail.gmail.com>
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
next prev parent reply index
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-10 15:58 Samuel Falvo II
2020-07-10 16:10 ` Luke Kenneth Casson Leighton [this message]
2020-07-10 16:54 ` Tobias Platen
2020-07-10 17:19 ` Luke Kenneth Casson Leighton
2020-07-10 21:47 ` Luke Kenneth Casson Leighton
2020-07-10 20:08 ` Luke Kenneth Casson Leighton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAPweEDxwWcbfvA331z0RkOdAfyUaDcGws+=JCF-OoidS6_f9SQ@mail.gmail.com' \
--to=lkcl@lkcl.net \
--cc=libre-riscv-dev@lists.libre-riscv.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Libre RISC-V Mailing list Archives (accessible via public-inbox)
Archives are clonable: git clone --mirror https://inbox.libre-soc.org/libre-riscv-dev
Example config snippet for mirrors
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git