Skip to content
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

MinGW, issue with VERILATOR_ROOT, verilator binary path #107

Open
sylefeb opened this issue Mar 27, 2024 · 3 comments
Open

MinGW, issue with VERILATOR_ROOT, verilator binary path #107

sylefeb opened this issue Mar 27, 2024 · 3 comments

Comments

@sylefeb
Copy link

sylefeb commented Mar 27, 2024

Platform: MinGW64

Problem: The Verilator binary exists in two locations (oss-cad-suite/share/verilator/bin/ and oss-cad-suite/bin), but using the one in oss-cad-suite/bin leads to an error VERILATOR_ROOT is set to inconsistent path. Suggest leaving it unset..

Since when: This seems to have been trigger on March 12 by commit 07326f2.

Workaround: Removing the binary from oss-cad-suite/bin and using the one in oss-cad-suite/share/verilator/bin/ works. [edit: ensuring the correct executable if found first in the path works too]

@davidar
Copy link

davidar commented Mar 30, 2024

I'm experiencing the same issue on linux-x64 (in my case the workaround has been unsetting the VERILATOR_ROOT variable set by oss-cad-suite/environment)

@gainbrain
Copy link

gainbrain commented May 14, 2024

Same here on darwin-x64. Apparently happened with commit 07326f2.

@davekeeshan
Copy link

This is what they have said about it on the verilator github #5047:

VERILATOR_ROOT is intended to point to the directory that contains the bin and include subdirectories, like in a source tree. This was always the intention, even before the change, and is describe in the installation manual here: https://github.com/verilator/verilator/blob/master/docs/guide/install.rst#1-run-in-place-from-verilator_root

You are using installation method 2 from here: https://github.com/verilator/verilator/blob/master/docs/guide/install.rst#2-install-into-a-specific-prefix Albeit it's not explicitly said, this does not require setting VERILATOR_ROOT. The scripts know what it should be, and hence the error if you set it to something inconsistent. As the error suggests, you should leave VERILATOR_ROOT unset and just run the verilator executable, it should take care of everything else for you.

If you want to know what VERILATOR_ROOT is (though ideally you shouldn't have to care), run verilator --getenv VERILATOR_ROOT

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants