-
Notifications
You must be signed in to change notification settings - Fork 680
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
System Requirements #387
System Requirements #387
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
My opinion is that we should prefer distro-managed packages over compiling/installing from scratch if the versions in the repos are sufficient. (I haven't tested myself yet, however.)
Also, if I recall correctly, verilator.mk should download and build its own Verilator, so installing it system-wide shouldn't be needed. |
Yes, that is true. Verilator is installed separately. |
Also if you can, on future commits can you add the |
This was tested on the official CentOS 7 and Ubuntu 18.04 AMIs: at least the toolchain build, Verilator sim of the default DUT, and FireMarshal br-base image build. |
Co-Authored-By: Albert Ou <aou@eecs.berkeley.edu>
This tries to make the system requirements a bit more clear, but providing two scripts for common Linux platforms (Centos/Ubuntu).