Closed PZZONE closed 1 year ago
The first message (about "anytree") is to do with how our tooling spots error messages. The message basically says "I don't think you have an add-on to Verible that you'd need, so I'm doing something simpler to parse the output".
Is there anything else that looks like an error to you? This looks to me like everything worked!
The first message (about "anytree") is to do with how our tooling spots error messages. The message basically says "I don't think you have an add-on to Verible that you'd need, so I'm doing something simpler to parse the output".
Is there anything else that looks like an error to you? This looks to me like everything worked!
Thank you so much for answering my question! ! ! I have installed Verible binary files before, and directly imported tools such as verible-* into the /opt/riscv/ path by decompression. The result of executing which verible-verilog-lint & verible-verilog-lint --version: All verible tools are as follows: So is this problem caused by incomplete configuration of my Verible environment?
I have to install the Verible by bazel for (https://github.com/chipsalliance/verible) and then i executing the command:
verible-verilog-lint --version
v0.0-3132-gb052efb1
Commit 2023-04-03
Built 2023-04-11T10:31:04Z
but when i run the command (make build-simple-system) , i have the same information : "No module named 'anytree" "Verible parser failed, using regex fallback instead."
When I searched for related issues, I found that there had been similar issues in the opentitan project. (This problem is caused by the version of fusesoc) I don't know how I need to find this problem, or try to modify it, can you give me some hints? (https://github.com/lowRISC/opentitan/issues/12769)
@rswarbrick ,Sorry to bother you again
Hi again! To be clear, this message isn't reporting a real problem: it's just saying that the tooling thinks it might flag some spurious errors (but it seems that it doesn't!). If this is the only thing you're noticing, there's not really anything for you to do. If there's a separate problem that you're seeing, maybe it's worth opening a new issue to avoid the problem getting hidden here.
Hi again! To be clear, this message isn't reporting a real problem: it's just saying that the tooling thinks it might flag some spurious errors (but it seems that it doesn't!). If this is the only thing you're noticing, there's not really anything for you to do. If there's a separate problem that you're seeing, maybe it's worth opening a new issue to avoid the problem getting hidden here.
Thank you very much !!! I guess my problem is that I didn't set reasonable parameters; reference to this https://github.com/lowRISC/ibex/issues/1866;
Observed Behavior ———————————————— The xrun command fails with:
this problem is : "No module named 'anytree" "Verible parser failed, using regex fallback instead." and then i running this command
My Environment Operating system: Ubuntu 22.04 Version of the Ibex source code: latest master branch 93c8e92 fusesoc /home/ysyx/.local/bin fusesoc 0.1
Steps to reproduce the issuet I have build the env for this (https://github.com/lowRISC/ibex/tree/master/examples/simple_system)